solidity icon indicating copy to clipboard operation
solidity copied to clipboard

Solidity, the Smart Contract Programming Language

Results 696 solidity issues
Sort by recently updated
recently updated
newest added

Came up with https://github.com/ethereum/solidity/issues/13512. We should aim for having this in the next release regardless of how we decide to deal with that issue. https://github.com/ethereum/solidity/issues/13512 should be the only relevant...

low effort
low impact
must have

## Description Function selectors can be used to initialize constants while error and event selectors (recently introduced in #12921) are rejected as non-constant. I think that all of them should...

bug :bug:
good first issue
language design :rage4:
medium difficulty
low effort
medium impact
must have

There is currently support for `verbatim`, allowing to instert arbitrary bytecode, but only when compiling in strict assembly mode. But the `verbatim` group of functions ios not available inside `assembly`...

language design :rage4:
medium effort
medium impact
must have eventually
needs design

This came up in https://github.com/ethereum/solidity/pull/13162#pullrequestreview-1101249411. Non-release builds of the compiler always output an extra warning, which results in a different output between release and debug builds in CI: ``` Warning:...

bug :bug:
good first issue
testing :hammer:
low effort
low impact
should have

Came up during fuzzing https://github.com/ethereum/solidity/pull/10015 This test case: https://gist.github.com/bshastry/06a1132d5bc47835284a0b5aaecf646a produces an ``InvalidDeposit`` error during the code transform, while it probably *should* emit a ``StackTooDeep`` error.

Closes https://github.com/ethereum/solidity/issues/11175. Closes https://github.com/ethereum/solidity/issues/9470.

Addresses #13497 - [x] Update code comment in `UnusedStoreEliminator.h` - [x] Check other undocumented optimizer steps

documentation :book:
optimizer

Came up in https://github.com/ethereum/solidity/pull/7589#discussion_r344259919. Is there a nice and easy way to have a pretty printing pass on the output? That would make those tests way easier to review.

good first issue
easy difficulty
testing :hammer:
low effort
low impact
should have