You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we're using a constant, but this constant is not guaranteed to be initialized during compilation.
Until that is fixed the following warning will remain in readme.md:
Warning
Although I haven't been able to recreate the issue yet, it seems that const values aren't guaranteed to be evaluated at compile time. This creates the issue that the group verification is not guaranteed to fail in its current implementation. I tried a workaround to force the compiler to evaluate the constant, but ran into this issue rust-lang/rust#60551.
If users need this guarantuee, they'll need to be able to at least opt into this behaviour.
Another solution is to add a way of testing this behaviour. I have some ideas for that, but I'll need some time to put them in writing.
Currently we're using a constant, but this constant is not guaranteed to be initialized during compilation.
Until that is fixed the following warning will remain in readme.md:
Warning
Although I haven't been able to recreate the issue yet, it seems that const values aren't guaranteed to be evaluated at compile time. This creates the issue that the group verification is not guaranteed to fail in its current implementation. I tried a workaround to force the compiler to evaluate the constant, but ran into this issue rust-lang/rust#60551.
If users need this guarantuee, they'll need to be able to at least opt into this behaviour.
Another solution is to add a way of testing this behaviour. I have some ideas for that, but I'll need some time to put them in writing.
I tried to define the problem in the following stack exchange question:
https://math.stackexchange.com/questions/4771133/finding-all-possible-valid-values-of-a-set-based-on-a-list-of-rules
In the future it might be necessary to optionally add a SAT solver if compilation proves to take up too much time.
This is possibly blocked by #16
The text was updated successfully, but these errors were encountered: