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
38 Open 51 Closed
38 Open 51 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

Functions that contain "unnamed return variables" should trigger a compiler error and not a warning. breaking change ⚠️ needs design The proposal is too vague to be implemented right away
#14017 opened Feb 25, 2023 by StErMi 0.9.0
4
Unable to use try/catch to catch local reverts in extra code generated for high-level external calls 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 must have Something we consider an essential part of Solidity 1.0. needs design The proposal is too vague to be implemented right away
#13869 opened Jan 12, 2023 by drortirosh
8
Statement has no effect warning should be emitted for view expressions. 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. needs design The proposal is too vague to be implemented right away
#13840 opened Jan 3, 2023 by 0xrisec
2
Data locations should be tied to types, not variable declarations. challenging difficulty 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. needs design The proposal is too vague to be implemented right away roadmap
#13730 opened Nov 21, 2022 by k06a
3
AST/asm import via Standard JSON 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. needs design The proposal is too vague to be implemented right away
#13690 opened Nov 8, 2022 by cameel
@aarlt
9
Check for reuse of old error/warning codes 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 testing 🔨
#13545 opened Sep 20, 2022 by frangio
1
Compile-Time-Constant expression evaluation has dependencies The PR depends on other PRs that must be merged first needs design The proposal is too vague to be implemented right away selected for development It's on our short-term development
#13318 opened Jul 28, 2022 by nishant-sachdeva
@ekpyron
Functions that are generic in the data location of pointer arguments 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
#13207 opened Jun 24, 2022 by frangio
1
Disallow complex expressions on left-hand-sides of assignments. breaking change ⚠️ 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. needs design The proposal is too vague to be implemented right away
#13147 opened Jun 15, 2022 by ekpyron
3
using for with explicit function names does not support overloaded functions 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
#13107 opened Jun 8, 2022 by adhusson
1
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
Tuple elements index access 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
#12635 opened Feb 5, 2022 by k06a
9
Don't require override(A, B) when inherited contracts already inherit from each other 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
#12554 opened Jan 18, 2022 by cameel
7
Better "stack too deep" errors annoys users 😢 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
#12449 opened Dec 22, 2021 by 134dd3v
8
Inline functions / closures / lambdas 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 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
#12297 opened Nov 19, 2021 by chriseth
3
Cannot link unqualified library names via Standard JSON breaking change ⚠️ 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. needs design The proposal is too vague to be implemented right away 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.
#12145 opened Oct 14, 2021 by cameel 0.9.0
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
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
Reconsider operators on ContractType 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 needs design The proposal is too vague to be implemented right away
#11700 opened Jul 27, 2021 by hrkrshnn
14
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
Conversions revamped 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 Something we consider an essential part of Solidity 1.0. needs design The proposal is too vague to be implemented right away
#11284 opened Apr 21, 2021 by axic
2
try/catch for custom errors 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 must have Something we consider an essential part of Solidity 1.0. needs design The proposal is too vague to be implemented right away
#11278 opened Apr 21, 2021 by hrkrshnn
15
try/catch for abi.decode() or abi.tryDecode 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 must have Something we consider an essential part of Solidity 1.0. needs design The proposal is too vague to be implemented right away
#10381 opened Nov 24, 2020 by gitpusha
13
Natspec: text before the @notice tag gets included as part of it 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. natspec needs design The proposal is too vague to be implemented right away
#10281 opened Nov 12, 2020 by axic
8
Expose sub-structure of bytecode 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 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 protocol design 🔮 Potential changes to ABI, meta data, standard JSON
#9332 opened Jul 7, 2020 by chriseth
11
ProTip! Follow long discussions with comments:>50.