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
Note that this feature could be very confusing to users of ink! version 3.0-rc5 and older since until then selector = value:string was allowed with value being of the form 0xC0DECAFE or some other hex-encoded u32 value in this particular form.
If a user does not update their codebase while jumping from ink! version 3.0-rc5 and a future version that implements this new evaluation feature for selectors the user's selectors will just silently change without notice.
Note that this feature could be very confusing to users of ink! version 3.0-rc5 and older since until then selector = value:string was allowed with value being of the form 0xC0DECAFE or some other hex-encoded u32 value in this particular form.
I agree with it. But I think we can create a workaround here. If we are able to parse the string into u32, then we should emit an error(that it is deprecated). But if it is not u32, so it is a user-defined string and we can calculate a hash form it.
It will be cool to have the ability to generate a selector inside of code and during the declaration of the selector.
During declaration of selector:
Somewhere in code:
The text was updated successfully, but these errors were encountered: