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
Since state is a reserved keyword in Truffle's guard mechanism, it should not be possible to use it in a guard definition as this can cause serious problems. The annotation processor should either reject the state keyword in guard definitions or the state temporary variable produced by the processor should be renamed to avoid this conflict.
Here's an example:
The text was updated successfully, but these errors were encountered:
Oh, forgot to mention that the class also has a state field which is shadowed by the int state value which is also bad.
Since one can get access to the Truffle state this way, I wonder if there are people actually doing this. I can't think of any good reason though, maybe because there isn't :)
Since
state
is a reserved keyword in Truffle's guard mechanism, it should not be possible to use it in a guard definition as this can cause serious problems. The annotation processor should either reject thestate
keyword in guard definitions or thestate
temporary variable produced by the processor should be renamed to avoid this conflict.Here's an example:
The text was updated successfully, but these errors were encountered: