Sean Young
Sean Young
I think there are few things that are needed. - The FileResolver should be wrapped in a `std::sync::RwLock` - Optionally the parse tree should be cached in the FileResolver, so...
> I think this issue is a bit more difficult than it looks like. If one file depends on the other, they cannot be built in parallel, due to dependency...
> File B.sol depends on A.sol. The semantic analysis can only happen for B after that contract A is fully resolved, even though they might generate different binaries. This is...
We need dapp examples
> hi i like to take this issue , so we need to just remove the duplicate the code Great, go for it! Please let us know if you have...
> Ideally, a user type should not exist in codegen. We would unwrap it when building the CFG. How would we add correct debug information to types if the higher...
@startup-dreamer looking forward to seeing a pull request
@startup-dreamer please follow the instructions at https://solang.readthedocs.io/en/latest/installing.html#step-1-install-the-llvm-libraries and do a `cargo clean`
Solang does support push/pop on memory arrays, even if solc does not. However, it should not panic.
You're right, we should have an `Expression::AddAssign` in the AST. There are a few other things we de-sugar which we should not, like `type()` functions.