Skip to content

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
401 Open 4,096 Closed
401 Open 4,096 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt click/return to exclude labels
or ⇧ click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Optimize ternary expressions to branchless code when cheaper. 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. must have Something we consider an essential part of Solidity 1.0. optimizer
#12930 opened Apr 13, 2022 by transmissions11
5 ❤️ 6
Add support for calldata input and output in abi.decode() high effort A lot to implement but still doable by a single person. The task is large or difficult. language design :rage4: Any changes to the language, e.g. new features 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.
#13518 opened Sep 12, 2022 by k06a
24 ❤️ 5
Remove .send and .transfer. breaking change ⚠️ high impact Changes are very prominent and affect users or the project in a major way. language design :rage4: Any changes to the language, e.g. new features low effort There is not much implementation work to be done. The task is very easy or tiny. needs design The proposal is too vague to be implemented right away
#7455 opened Sep 19, 2019 by MicahZoltu 0.9.0
25 ❤️ 3
IPFS hash feature use non-specified algorithm which is not widely compatible in the ecosystem bug 🐛
#14389 opened Jul 8, 2023 by Jorropo
2 ❤️ 3
Support for CodeSection type for linking externally written/compiled bytecode with EOF supported Solidity contracts. feature
#15211 opened Jun 21, 2024 by AmadiMichael
1 ❤️ 2
Remove uint as alias for uint256 breaking change ⚠️ feature language design :rage4: Any changes to the language, e.g. new features low effort There is not much implementation work to be done. The task is very easy or tiny. medium impact Default level of impact 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.
#14026 opened Mar 4, 2023 by pcaversaccio 0.9.0
17 ❤️ 2
Should private functions really clash ? bounty worthy 💰 help wanted 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. 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.
#11889 opened Sep 3, 2021 by Amxx
1
39 ❤️ 1
Enough Debugging data for tools to switch to via-IR epic ethdebug roadmap viair
#13720 opened Nov 17, 2022 by NunoFilipeSantos
4 of 6 tasks
7 ❤️ 1
Ranked overload resolution language design :rage4: Any changes to the language, e.g. new features medium effort Default level of effort medium impact Default level of impact must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it. needs design The proposal is too vague to be implemented right away
#1256 opened Oct 20, 2016 by chriseth
13 ❤️ 1
Generics Implementation epic generics roadmap
#13776 opened Dec 2, 2022 by NunoFilipeSantos
1 ❤️ 1
Allow specifying storage locations language design :rage4: Any changes to the language, e.g. new features must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#597 opened May 25, 2016 by pipermerriam 0.8.28
78
Enums with data / sum datatype / algebraic datatypes 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. language design :rage4: Any changes to the language, e.g. new features needs design The proposal is too vague to be implemented right away selected for development It's on our short-term development
#909 opened Aug 16, 2016 by chriseth
14
Short notation for function types high impact Changes are very prominent and affect users or the project in a major way. language design :rage4: Any changes to the language, e.g. new features 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. needs design The proposal is too vague to be implemented right away roadmap
#1349 opened Nov 9, 2016 by chriseth
6
Make copy / reference semantics more explicit breaking change ⚠️ 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. language design :rage4: Any changes to the language, e.g. new features needs design The proposal is too vague to be implemented right away selected for development It's on our short-term development
#2435 opened Jun 21, 2017 by chriseth
11
Syntax to refer to a specific overload of a function language design :rage4: Any changes to the language, e.g. new features medium effort Default level of effort medium impact Default level of impact must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it. needs design The proposal is too vague to be implemented right away
#3556 opened Feb 20, 2018 by axic
29
ABI: Event selectors do not distinguish indexed arguments bug 🐛 protocol design 🔮 Potential changes to ABI, meta data, standard JSON
#4168 opened May 21, 2018 by frangio
7
behavior of named arguments in function types bug 🐛 low impact Changes are not very noticeable or potential benefits are limited. medium effort Default level of effort
#4299 opened Jun 14, 2018 by ekpyron
4
Add new external tests 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. must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it. testing 🔨
#5956 opened Feb 7, 2019 by chriseth
19
Add .exists() and .iscontract() on to the address type language design :rage4: Any changes to the language, e.g. new features
#4910 opened Sep 5, 2018 by axic
13
[SMTChecker] Loop invariants smt
#6210 opened Mar 6, 2019 by leonardoalt
7
[soltest] Incorrect semantics tests suggestions for unaligned hex strings. bug 🐛 testing 🔨
#6703 opened May 8, 2019 by ekpyron
2
Unable to check existence of precompiled contract by its address or get its code in VM or Sepolia testnet bug 🐛
#15428 opened Sep 12, 2024 by amit-supraoracles
Rethink (or maybe even remove?) super breaking change ⚠️ high impact Changes are very prominent and affect users or the project in a major way. language design :rage4: Any changes to the language, e.g. new features 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. needs design The proposal is too vague to be implemented right away
#7261 opened Aug 14, 2019 by ekpyron
17
Specification of ABI decoding (especially padding in bytes) documentation 📖 medium effort Default level of effort medium impact Default level of impact must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#6978 opened Jun 20, 2019 by sifmelcara
8
[isoltest] Formatting should support strings longer than 32 bytes bug 🐛 low impact Changes are not very noticeable or potential benefits are limited. medium effort Default level of effort should compile without error Error is reported even though it shouldn't. Source is fine. should have We like the idea but it’s not important enough to be a part of the roadmap. testing 🔨
#7197 opened Aug 7, 2019 by erak
5
ProTip! no:milestone will show everything without a milestone.