-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Some EOF-specific Yul builtin names are reserved even outside of EOF
bug 🐛
low effort
There is not much implementation work to be done. The task is very easy or tiny.
medium impact
Default level of impact
should compile without error
Error is reported even though it shouldn't. Source is fine.
Running syntax tests via IR
low impact
Changes are not very noticeable or potential benefits are limited.
medium effort
Default level of effort
must have eventually
Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
testing 🔨
#15670
opened Dec 20, 2024 by
cameel
IR codegen does not implement access to library address by contract name
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.
#15669
opened Dec 20, 2024 by
cameel
ICE in
SolverInterface.cpp
: Trying to create an 'equal' expression with different sorts
bug 🐛
smt
#15647
opened Dec 16, 2024 by
haoyang9804
Repeated error message caused by omitting "--via-ir"
bug 🐛
#15646
opened Dec 16, 2024 by
haoyang9804
Inconsistent defaults of There is not much implementation work to be done. The task is very easy or tiny.
medium impact
Default level of impact
optimizeStackAllocation
flag cause ICEs and metadata issues in optimized compilation with Yul optimizer disabled
bug 🐛
low effort
#15641
opened Dec 12, 2024 by
P1umH0
Do not set freemem pointer when having only fallback function with sole assembly block
feature
#15627
opened Dec 9, 2024 by
radeksvarz
Bump evmone to 0.13.0 and define Osaka as a supported EVM version
EOF
high impact
Changes are very prominent and affect users or the project in a major way.
low effort
There is not much implementation work to be done. The task is very easy or tiny.
must have
Something we consider an essential part of Solidity 1.0.
#15622
opened Dec 6, 2024 by
cameel
Add Support for Compiling and Deploying First Class Functions
feature
#15621
opened Dec 6, 2024 by
cre-mer
Rename the Solidity contract metadata.json to Blueprint
feature
#15614
opened Dec 5, 2024 by
kuzdogan
SMTChecker:the description of model-checker-timeout does not match the actual behavior.
documentation 📖
#15609
opened Dec 3, 2024 by
Subway2023
SMTChecker: Cross-contract function calls cause the BMC model to crash.
bug 🐛
#15605
opened Dec 2, 2024 by
Subway2023
Assigning values to bytes causes an ABICoder v1 decoding exception.
bug 🐛
#15604
opened Dec 2, 2024 by
Subway2023
SMTChecker: SMT logic error caused by assigning values to a fixed-size array.
bug 🐛
#15603
opened Dec 2, 2024 by
Subway2023
Manipulating multi-dimensional arrays causes IR-based code generation to return incorrect values.
bug 🐛
#15602
opened Dec 2, 2024 by
Subway2023
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 "Internal or recursive type is not allowed for public state variables" causes confusion
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 report better error
Error is just badly reported. Should be a proper type error - source is not fine.
#15583
opened Nov 22, 2024 by
haoyang9804
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-11-24.