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
The Vyper compiler currently disallows defining the fallback function __default__() as part of an interface definition. E.g. the following contract will raise with:
This can become problematic, if you want to enforce custom interface definitions (e.g. my snekmate timelock_controller could be transformed into an interface, which would require __default__() to be complete). There might also be some EIPs or future EIPs that require this. We should discuss here if we should lift this restriction or not.
The text was updated successfully, but these errors were encountered:
Summary
The Vyper compiler currently disallows defining the fallback function
__default__()
as part of an interface definition. E.g. the following contract will raise with:This can become problematic, if you want to enforce custom interface definitions (e.g. my snekmate
timelock_controller
could be transformed into an interface, which would require__default__()
to be complete). There might also be some EIPs or future EIPs that require this. We should discuss here if we should lift this restriction or not.The text was updated successfully, but these errors were encountered: