xermicus
xermicus
If an event has fields declared indexed, they should be passed into the Substrate topics. This is not implemented correctly today. Ensure that indexed fields are passed into topics and...
In order to fix [this issue](https://github.com/paritytech/cargo-contract/issues/659) together with [this change](https://github.com/paritytech/scale-info/pull/164/), we want to enable metadata construction at runtime. In Solang, we'd like to rely on the official `ink!` crates instead...
Found a case where Solang (latest commit on `main`) generates invalid code, failing an LLVM assertion. [Code is from here](https://github.com/adlerjohn/inflate-sol/blob/master/contracts/InflateLib.sol) but I extracted a minimal reproducer below which is enough...
While working on the tornado integration test, I came across this Solidity implementation. It was so slow that it wasn't even usable: It broke the merkle tree implementation for heights...
I noticed that the dispatch code no longer has a special case where if all functions are non-payable, then there is a single value transfer check which is both less...
Working with our [CFG `Expression`s](https://github.com/hyperledger/solang/blob/main/src/codegen/mod.rs#L375) is not very intuitive ATM. Individual `Expression` variants deserve comments to provide a bit of context, e.g. describing their fields and maybe other things to...
We are not very consistent about how we use `Solidity` in our docs. We just use `Solidity`, sometimes `Solang Solidity`, `Solidity on Solana`, `Ethereum Solidity` etc... This leads to discussions...
While implementing of #1449, it became apparent that Solang does not use all the `Panic` codes Solidity knows. Maybe this is fine because for our currently supported targets, it doesn't...
As we don't use `AllocDynamicBytes`, we could just have an `Expression::StringLiteral` to cover this case. _Originally posted by @LucasSte in https://github.com/hyperledger/solang/pull/1449#discussion_r1269462467_ This would be useful in a number of places,...