In interfaces/implementations which randomize the values with crypto/rand.Reader, we should handle the errors. By default it never errors on Linux, but may on other platforms. I guess having alternative methods Must... which either randomize values or panic, could work.

With that, it would be beneficial to check all downstream usage of SetRandom methods in gnark/gnark-crypto and change accordingly.