Skip to content
New issue

0.8.30

Open
No due date
Last updated Apr 8, 2025
18% complete

List view

0 issues of 13 selected

  • Bytecode compare runs with two-stage compilation

    medium effortDefault level of effort
    medium impactDefault level of impact
    must haveSomething we consider an essential part of Solidity 1.0.
    testing 🔨
    Status: Open.
    #15063 In ethereum/solidity;
    · cameel opened on Apr 26, 2024

  • Promote custom errors to proper types.

    high effortA lot to implement but still doable by a single person. The task is large or difficult.
    medium impactDefault level of impact
    selected for developmentIt's on our short-term development
    Status: Open.
    #15388 In ethereum/solidity;
    · ekpyron opened on Sep 2, 2024

  • Insufficient check for uninitialized storage pointer access

    bug 🐛
    low effortThere is not much implementation work to be done. The task is very easy or tiny.
    low impactChanges are not very noticeable or potential benefits are limited.
    must have eventuallySomething we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
    should report errorCompiles without errors but should not.
    Status: Open.
    #14021 In ethereum/solidity;
    · qwaz-theori opened on Mar 2, 2023

  • IPFS hash feature use non-specified algorithm which is not widely compatible in the ecosystem

    bug 🐛
    Status: Open.
    #14389 In ethereum/solidity;
    · Jorropo opened on Jul 8, 2023

  • Deprecation warnings for features we plan to remove

    low effortThere is not much implementation work to be done. The task is very easy or tiny.
    medium impactDefault level of impact
    selected for developmentIt's on our short-term development
    Status: Open.
    #15795 In ethereum/solidity;
    · cameel opened on Jan 29, 2025

  • Inconsistent defaults of <code>optimizeStackAllocation</code> flag cause ICEs and metadata issues in optimized compilation with Yul optimizer disabled

    bug 🐛
    low effortThere is not much implementation work to be done. The task is very easy or tiny.
    medium impactDefault level of impact
    Status: Open.
    #15641 In ethereum/solidity;
    · P1umH0 opened on Dec 12, 2024

  • Bump docker ubuntu ossfuzz image to use evmone v14.

    bug 🐛
    medium effortDefault level of effort
    medium impactDefault level of impact
    testing 🔨
    Status: Open.
    #15338 In ethereum/solidity;
    · nikola-matic opened on Aug 16, 2024

  • Local environment setup failed with Python 3.13.1 due to <code>No module named 'imghdr'</code>

    documentation 📖
    Status: Open.
    #15811 In ethereum/solidity;
    · codersjj opened on Feb 1, 2025

  • Fix Ubuntu 2025-04 "Plucky" builds

    build system 🏗️
    selected for developmentIt's on our short-term development
    Status: Open.
    #15936 In ethereum/solidity;
    · ekpyron opened on Mar 12, 2025

  • Introduce subassembly offset output artifact

    Status: Open (in progress).
    ethereum/soliditynumber 15710
    #15710 In ethereum/solidity;
    · nikola-matic opened on Jan 13, 2025

  • Inconsistent Treatment of Storage Arrays on the Slot Overflow Boundary

    bug 🐛
    low impactChanges are not very noticeable or potential benefits are limited.
    medium effortDefault level of effort
    must haveSomething we consider an essential part of Solidity 1.0.
    Status: Open.
    #15587 In ethereum/solidity;
    · ekpyron opened on Nov 25, 2024

  • Inconsistent subassembly object ID for different sizes of size_t

    bug 🐛
    Status: Open.
    #15953 In ethereum/solidity;
    · clonker opened on Mar 17, 2025

  • Fix array assignment and deletion at storage slot overflow boundary

    Status: Draft (not ready).
    ethereum/soliditynumber 15984
    #15984 In ethereum/solidity;
    · r0qs opened on Apr 7, 2025
    •