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

475 Open 5,622 Closed
475 Open 5,622 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

Invalid and inconsistent types in ABIs for library functions documentation 📖 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. protocol design 🔮 Potential changes to ABI, meta data, standard JSON
#9278 opened Jul 1, 2020 by haltman-at
12
[SMTChecker] Support memory/storage pointers smt
#9148 opened Jun 8, 2020 by leonardoalt
3
Optimization possibility of memory usage for loops 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. needs design The proposal is too vague to be implemented right away optimizer selected for development It's on our short-term development
#9046 opened May 27, 2020 by daejunpark
3
Document the wasm releases documentation 📖 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. solcbin
#9015 opened May 25, 2020 by chriseth
1
Documentation issue: Cleaning up some other types documentation 📖 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 Something we consider an essential part of Solidity 1.0.
#8876 opened May 7, 2020 by haltman-at
1
Some issues with modifier depth
#8842 opened May 5, 2020 by haltman-at 0.9.0
6
Change setimmutable Yul builtin to reference code object, or use special codecopy version that does the replacement.. language design :rage4: Any changes to the language, e.g. new features
#8826 opened May 4, 2020 by ekpyron 0.9.0
2
[SMTChecker] Tune Spacer options smt
#8755 opened Apr 23, 2020 by leonardoalt
[SMTChecker] Make command line tests aware of SMT solvers smt testing 🔨
#8473 opened Mar 10, 2020 by leonardoalt
1
Verify and potentially increase test coverage for inheritance and function calls. 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 🔨
#8437 opened Mar 6, 2020 by ekpyron
3
ICE in ArrayType::calldataEncodedSize(bool) [Array size does not fit unsigned] bug 🐛 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. should report better error Error is just badly reported. Should be a proper type error - source is not fine.
#8382 opened Feb 25, 2020 by agroce
1
10
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
[SMTChecker] Support function type smt
#8330 opened Feb 17, 2020 by leonardoalt
@pgebal
1
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
[SMTChecker] Rerun tests from Solc-Verify 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. smt testing 🔨
#8145 opened Jan 15, 2020 by leonardoalt
2
Support nested objects for Yul tests. 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. testing 🔨
#8143 opened Jan 15, 2020 by chriseth
Extend ABI documentation of function types 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.
#7931 opened Dec 9, 2019 by digulla
2
ABI does not contain sufficient information to compute the correct function selector bug 🐛 protocol design 🔮 Potential changes to ABI, meta data, standard JSON
#7530 opened Oct 10, 2019 by gsalzer
7
Replace rule list with "DSL" high effort A lot to implement but still doable by a single person. The task is large or difficult. 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. optimizer refactor
#7520 opened Oct 7, 2019 by ekpyron
13
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
Array slices for memory and storage arrays. 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.
#7423 opened Sep 13, 2019 by ekpyron
5
[SMTChecker] Refactor pointers easy difficulty good first issue candidate Could be a "good first issue" but something is blocking it or it has open questions. smt
#7266 opened Aug 15, 2019 by leonardoalt
8
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
[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
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
ProTip! no:milestone will show everything without a milestone.