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

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
Fixed point types epic effort Multi-stage task that may require coordination between team members across multiple PRs. 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 selected for development It's on our short-term development
#409 opened Mar 3, 2016 by chriseth
4 of 7 tasks
2
78
Constant-complexity dispatcher idea must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#12650 opened Feb 8, 2022 by k06a
48
Immutable dynamic arrays 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 selected for development It's on our short-term development
#12587 opened Jan 26, 2022 by nventuro
44
templates / generics epic effort Multi-stage task that may require coordination between team members across multiple PRs. generics 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
#869 opened Aug 11, 2016 by chriseth
41
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
Assembly language feature: add new levels for Yul language design :rage4: Any changes to the language, e.g. new features
#13247 opened Jul 5, 2022 by pcaversaccio
36
[CLI] Drop --combined-json option and direct users to standard json breaking change ⚠️ low effort There is not much implementation work to be done. The task is very easy or tiny. 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.
#10278 opened Nov 12, 2020 by axic
31
Support Apple Silicon in Release Builds build system 🏗️ 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. solcbin
#12291 opened Nov 16, 2021 by xanderdunn
29
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
Allow verbatim in Solidity assembly blocks 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
#12067 opened Sep 30, 2021 by dessaya
27
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
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
Allow nonpayable functions to override payable functions 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. low impact Changes are not very noticeable or potential benefits are limited. medium difficulty must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#11253 opened Apr 13, 2021 by frangio
23
Support EIP-712 typehash in type feature
#14157 opened Apr 26, 2023 by k06a
21
Ability to override function selectors to support external interfaces not expressible in valid syntax. 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 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
#11819 opened Aug 18, 2021 by ekpyron
21
immutable for libraries / dynamic libraries / high-level delegatecall 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
#11695 opened Jul 26, 2021 by chriseth
21
try/catch doesn't catch some call errors. breaking change ⚠️ 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 Something we consider an essential part of Solidity 1.0. needs design The proposal is too vague to be implemented right away
#12725 opened Mar 1, 2022 by drortirosh
20
Replace commit_hash.txt with git archive placeholders (and try also replacing prerelease.txt) build system 🏗️ documentation 📖 medium effort Default level of effort medium impact Default level of impact must have Something we consider an essential part of Solidity 1.0.
#9720 opened Sep 1, 2020 by ekpyron
1
20
Inconsistent library address validations between CLI and Standard JSON bug 🐛 easy difficulty 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. should have We like the idea but it’s not important enough to be a part of the roadmap.
#10299 opened Nov 14, 2020 by cameel
2
19
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
Wrong evaluation order of arguments to parent constructors breaking change ⚠️ language design :rage4: Any changes to the language, e.g. new features low impact Changes are not very noticeable or potential benefits are limited. medium effort Default level of effort
#10480 opened Dec 2, 2020 by frangio 0.9.0
18
Standard library selected for development It's on our short-term development stdlib
#10282 opened Nov 12, 2020 by axic
18
Arbitrary order of contracts in override specifier is confusing. annoys users 😢 breaking change ⚠️ 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. needs design The proposal is too vague to be implemented right away
#8354 opened Feb 20, 2020 by apguerrera
18
static_assert and static_require 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
#8146 opened Jan 15, 2020 by leonardoalt
18
ProTip! Follow long discussions with comments:>50.