-
Notifications
You must be signed in to change notification settings - Fork 23
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
Declaring a top-level payable
constant results in CompileInferenceError
#255
Comments
Hey @blitz-1306, pinging you because you've helped us before. Any chance you could take a look at this issue? Huge thanks in advance 🙏🏻 |
@gas1cent Hello there and thanks for the input. I will look into it and provide feedback on this week. If there would be a fix, it would likely arrive on next week. |
Okay, this is clearly a bug related to a file-level definitons parser, that we use to preprocess imports. I will look into a possible solution. Stay tuned. |
See #256 with the bugfix. I believe we should be able to deliver it soon enough. |
Environment
Latest release, v18.1.1
Scenario
When a
payable
constant is defined outside of a contract, the compiler throws aCompileInferenceError
. No error is thrown in the same scenario but withoutpayable
.To test put the following in
sample.sol
:Then try to compile:
Expected behavior
Successful compilation.
Current behavior
The text was updated successfully, but these errors were encountered: