Arya Tabaie

I guess it is better to say of _each_ type: ```go type Foo uint64 func (f* Foo) hello() {} func (f Foo) goodbye() {} ```

Makes sense, thank you!

@ivokub @yelhousni Does this make sense? Does it address what https://github.com/ConsenSys/gnark-crypto/pull/312 is about? If we reach consensus here I think we can skip the Wednesday meeting. 😁

@ivokub I agree with your argument for key options vs many parameters, and I'm starting to doubt the necessity of exposing a "sign custom string" function in the first place....

Thank you for the prompt response. I tried the following `cmake` script: ```cmake project(emp_zk_compile_err) set(CMAKE_CXX_STANDARD 17) add_executable(emp_zk_compile_err main.cpp) target_include_directories(emp_zk_compile_err PUBLIC "/path/emp-zk") target_include_directories(emp_zk_compile_err PUBLIC "/path/emp-tool") target_include_directories(emp_zk_compile_err PUBLIC "/path/emp-ot") target_include_directories(emp_zk_compile_err PUBLIC "/usr/local/opt/[email protected]/include")...

> so instead of hardcoding `SolverSucceeded` I think it is reasonable to always expect success. A single function is simpler than a whole circuit in that rather than succeeding or...

Ah I see. Yes agreed that that's desirable.

~@jpnovais the Kotlin side is probably all wrong. I was hoping to hammer that part out together with yourself or @gauravahuja.~ ^ seems like you've already done all that. I'll...

Closed in favor of https://github.com/Consensys/linea-monorepo/pull/229 due to merge conflicts

Thank you for the contribution! Am I understanding correctly that the hash and rand settings are global? Since the `mpcsetup` package is so new, I wouldn't worry about backwards compatibility...