-
Notifications
You must be signed in to change notification settings - Fork 125
Allow halo2 constraint names to have non-static names #65
Comments
I don't think we have to follow |
So Gate originally has fields with 'static lifetime:
If we want
Then we get this error because s gets dropped. But if we use a static String type, what's the point of making this change? |
An alternative way is to change Gate, with either
To solve this we must change OtherType following the same 'a lifetime or use String, and that results in changing many struct in Halo2. |
Yeah I was thinking of converting from whatever the input it (static string or String already) to String and then just store that String. That requires a lot of changes? |
Should be backward-compatible so should still be able to directly take a static string.
Something that can take a non-static string in halo2 is
assign_advice
, so may be good to take a look at that how it's done there. Otherwise using the<S: AsRef<str>>
generic` may work.Things to change:
create_gate
functionlookup
functionlookup_any
functionconstraint_names
field inGate
The text was updated successfully, but these errors were encountered: