Error when running SC on contracts using experimental ABIEncoderV2
See original GitHub issueI am running Solidity Coverage on a contract that uses structs with experimental ABIEncoderV2. The contract compiles and runs on Truffle, but when I run SC on it I get the following error:
SyntaxError: Expected comment, end of line, string, or whitespace but "A" found. Line: 2, Column: 21 Exiting without generating coverage...
The line where SC crashes is the following:
pragma experimental ABIEncoderV2;
I am currently running solidity-coverage version 0.4.15. Let me know if there is any more information I can provide.
Thanks,
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
ABIEncoderV2 runs into stack too deep · Issue #10930 - GitHub
Compiling contract raises strange error from solc but solc does not complain when run directly eth-brownie/brownie#1147.
Read more >This type is only supported in the new experimental ABI ...
The error is telling you to add an additional line to the top of your code: pragma experimental ABIEncoderV2;. This feature came in...
Read more >sc-forks/solidity-coverage - Gitter
@cgewecke The contract compiles and runs on Truffle. It's crashing on the 'pragma experimental ABIEncoderV2' line at the start of the file. The...
Read more >Solidity Optimizer and ABIEncoderV2 Bugs
An unexpectedly high count of contracts compiled with the experimental encoder were found deployed on mainnet, many without verified source-code ...
Read more >Generating Ethereum Smart Contracts from DasContract ...
Blockchain smart contracts (SC) are an emerging technology that ... pragma experimental ABIEncoderV2 is used for decoding nested struc-.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@marinatorras Thank you, perfect. Will fix in the next couple days.
@marinatorras This should be fixed in
0.5.5
- thanks for reporting and apologies for the delay.