-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Issues: ethereum/solidity
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Inconsistent Treatment of Storage Arrays on the Slot Overflow Boundary
bug 🐛
low impact
Changes are not very noticeable or potential benefits are limited.
medium effort
Default level of effort
must have
Something we consider an essential part of Solidity 1.0.
#15587
opened Nov 25, 2024 by
ekpyron
msg.data, calldataload, calldatasize not available in constructor but no error in compiler
bug 🐛
#15585
opened Nov 22, 2024 by
3esmit
Error message "recursive type is not allowed for public state variables" causes confusion
bug 🐛
#15583
opened Nov 22, 2024 by
haoyang9804
Incorrect error message when declaring storage parameters public functions
bug 🐛
#15567
opened Nov 4, 2024 by
haoyang9804
Reversing the order of two in-contract functions causes two different error messages
bug 🐛
#15565
opened Nov 4, 2024 by
haoyang9804
Error message inconsistency caused by in-function mapping declaration
bug 🐛
#15564
opened Nov 3, 2024 by
haoyang9804
Different error codes are produced by solc under different optimization parameters
bug 🐛
#15553
opened Oct 30, 2024 by
lum7na
Yul object names with dots are accepted but ambiguous
bug 🐛
low effort
There is not much implementation work to be done. The task is very easy or tiny.
low impact
Changes are not very noticeable or potential benefits are limited.
must have eventually
Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#15540
opened Oct 23, 2024 by
cameel
Document Assembly/Solidity Masking Behaviour and via-IR/legacy differences in it
documentation 📖
medium effort
Default level of effort
medium impact
Default level of impact
selected for development
It's on our short-term development
#15531
opened Oct 21, 2024 by
ekpyron
Could not determine the version of z3, since the z3 executable was not found.
waiting for more input
Issues waiting for more input by the reporter
#15515
opened Oct 15, 2024 by
hongyu-gui
Performance improvements of individual Yul Optimizer steps
high effort
A lot to implement but still doable by a single person. The task is large or difficult.
high impact
Changes are very prominent and affect users or the project in a major way.
optimizer
performance 🐎
selected for development
It's on our short-term development
#15508
opened Oct 11, 2024 by
cameel
3 of 4 tasks
Update release docker builds scripts/docker_deploy_manual.sh
build system 🏗️
selected for development
It's on our short-term development
The type system seems to be awkward in handling data location in tenery operation
bug 🐛
#15486
opened Oct 7, 2024 by
haoyang9804
use before assignment of calldata struct instance inside a function does not throw an error
bug 🐛
#15483
opened Oct 7, 2024 by
haoyang9804
non-address hex literals cannot be assigned to uint256
bug 🐛
#15468
opened Sep 30, 2024 by
haoyang9804
Undefined behaviour: Copying struct/class with uninitialized members
bug 🐛
#15462
opened Sep 27, 2024 by
hribz
ICE when loading the same file multiple times via import callback
bug 🐛
low effort
There is not much implementation work to be done. The task is very easy or tiny.
low impact
Changes are not very noticeable or potential benefits are limited.
must have eventually
Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
should compile without error
Error is reported even though it shouldn't. Source is fine.
#15458
opened Sep 25, 2024 by
cameel
do-while results in redundant branching instructions when compiling via IR
low impact
Changes are not very noticeable or potential benefits are limited.
medium effort
Default level of effort
nice to have
We don’t see a good reason not to have it but won’t go out of our way to implement it.
optimizer
#15442
opened Sep 19, 2024 by
Philogy
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.