Alex Beregszaszi
Alex Beregszaszi
```solidity contract C { function f() { require(balanceOf(); } } ``` results in ``` [error] contracts/A.sol: TypeError: Cannot read property 'length' of undefined [error] at ASTBuilder.visitExpression (/node_modules/@solidity-parser/parser/dist/index.cjs.js:36002:26) [error] at ASTBuilder.visitExpressionStatement...
Use `solc.license()` to retrieve the text - it will be **very** long though. Depends on https://github.com/ethereum/solc-js/pull/121.
Since it is possible to set up the tree such that it will perform hashing: ``` const merkleTree = new MerkleTree(elements, keccak256, { hashLeaves: true }); ``` I think it...
Since the Solidity repository maintains the ANTLR grammar which originated from here and it is kept up to date with the language, perhaps it would make sense considering to use...
### Describe the issue: This is probably related to #1173. Some detectors, like `delegatecall_in_loop`, crash the parser with some custom error cases. ### Code example to reproduce the issue: This...
### Describe the issue: Custom errors which have contracts/interface types as arguments are not support properly. ### Code example to reproduce the issue: ```solidity interface K { } interface I...
A couple of simple tests can be added to cover `index.js` (except the `fromV1` function). Covering `thirdparty.js` is secondary.
See https://github.com/lexansoft/ethcracker/tree/master/src/accounts/keystore/testdata
It would be nice to have hevm integrated into the [FuzzyVM](https://github.com/MariusVanDerWijden/FuzzyVM) ([blog post](https://mariusvanderwijden.github.io/blog/2021/05/02/FuzzyVM/)) effort. The first step towards that would be implementing tracing output akin to [EIP-3155](https://eips.ethereum.org/EIPS/eip-3155).
Solidity has a JSON-based interface written in C to compiler contracts. The input is a JSON formatted list of contracts and the output is a JSON with bytecode, assembly, etc....