Allow constants in interfaces #8775
Labels
closed due inactivity
The issue/PR was automatically closed due to inactivity.
language design
Any changes to the language, e.g. new features
low effort
There is not much implementation work to be done. The task is very easy or tiny.
medium impact
Default level of impact
stale
The issue/PR was marked as stale because it has been open for too long.
(Moved this from #3411 which, now confusingly, refers to a different feature.)
Since we allow accessing constants through contract names (#1290) and enums in interfaces (#4087), it may make sense to reconsider this feature, at least for some healthy discussion.
I am still not sure if it is a good idea or not (it definitely can be useful from a users' perspective, but could be dangerous?)
The case I ran into is the following (ralexstokes/deposit-verifier#2):
In this example the interface uses basic types (
bytes
), but they have a limit enforced (the two constant above) so it would be useful from the caller to haverequire
statements:The text was updated successfully, but these errors were encountered: