Labels

• language server
• 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
• medium effort

  Default level of effort
• medium impact

  Default level of impact
• must have

  Something we consider an essential part of Solidity 1.0.
• must have eventually

  Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
• natspec
• needs design

  The proposal is too vague to be implemented right away
• needs investigation
• 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.
• optimizer
• outsourceable

  Needs little knowledge about the code base and can be done by externals.
• performance 🐎
• priority review

  We want this get the review of this PR to a conclusion ASAP.
• protocol design 🔮

  Potential changes to ABI, meta data, standard JSON
• refactor
• research
• roadmap
• selected for development

  It's on our short-term development
• 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.
• should report better error

  Error is just badly reported. Should be a proper type error - source is not fine.
• should report error

  Compiles without errors but should not.
• smt
• solcbin
• solcjs
• spam
• stale

  The issue/PR was marked as stale because it has been open for too long.