-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AddressType wrongly accepts just payable
state mutability as the whole type
#654
Labels
bug
Something isn't working
Comments
OmarTawfik
added a commit
to OmarTawfik-forks/slang
that referenced
this issue
Jan 28, 2024
Removes `payable` as an elementary type, adding it back to primary expressions (to be parsed as the base of a call expression). More details in NomicFoundation#654 Closes NomicFoundation#654
OmarTawfik
added a commit
to OmarTawfik-forks/slang
that referenced
this issue
Jan 28, 2024
Removes `payable` as an elementary type, adding it back to primary expressions (to be parsed as the base of a call expression). More details in NomicFoundation#654 Closes NomicFoundation#654
OmarTawfik
added a commit
to OmarTawfik-forks/slang
that referenced
this issue
Jan 28, 2024
Removes `payable` as an elementary type, adding it back to primary expressions (to be parsed as the base of a call expression). More details in NomicFoundation#654 Closes NomicFoundation#654
OmarTawfik
added a commit
to OmarTawfik-forks/slang
that referenced
this issue
Feb 3, 2024
Removes `payable` as an elementary type, adding it back to primary expressions (to be parsed as the base of a call expression). More details in NomicFoundation#654 Closes NomicFoundation#654
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
YAML spec
DSL v1
DSL v2
but
ElementaryType
acceptsPayableKeyword
alongsideAddressType
.The address type should be
address (payable)
. There is alsopayable(<address>)
conversion expression but that should be handled separately, aspayable
on its own is not an elementary type.The text was updated successfully, but these errors were encountered: