Solidity

Solidity currently allows executing the delete operator on structs like EnumerableSet and EnumerableMap even though they contain a mapping that will not be cleared, and the operation will in fact corrupt the struct's data.

According to ethereum/solidity#11843 this operation will no longer be allowed in Solidity 0.9, but in the meantime we should document that `dele

Description

Suppose I try to compile the following contract:

//SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract Repro {
  function run() public pure returns (string memory) {
    return "¡¡¡";
  }
}

I get the following error message:

ParserError: Invalid character in string.
 --> project:/contracts/Repro.sol:6:12:
  |
6 |     return "¡¡

Feature

Similar to #4461, it would be nice if people could truffle exec typescript without needing to run a compilation step.

Steps to Reproduce

Write a script for truffle exec in TypeScript

Desired Behavior

Truffle would use ts-node to execute said script

Current Behavior

Users must first compile said script, and truffle exec the compilation output.

Description

Change links and references in the docs to run an Ethereum node from parity to openethereum, and change these references in the code too.

Motivation

Currently, docs about running an Ethereum node states that you can use parity-ethereum, but the project is no longer maintained.

There's also lots of comments and b

It is currently not possible to specify the chain ID for a hardhat network invoked with npx hardhat node through any means other than the config file. This means it is impossible to specify the --chain-id argument in the command line, or execute a chain host pragmatically with hre.run('node', { chainId: 100 }).

Please add the chainId parameter to the node command so it is possible to

Component

Forge

Describe the feature you would like

Currently vm.expectCall operates on a target address and the calldata it expects

 function expectCall(address,bytes calldata) external;

When sending ETH through multiple contracts, it would be useful to have an overloaded expectCall that also accepts a value param that also asserts on call context's value

If we give Echidna valid ranges for enum types, it will spend less time producing invalid calldata and possibly help reach greater coverage (at the very least in less runs). For each contract, produce a list of valid ranges for each enum range.

TBD:
what format would be ideal @ggrieco-tob?

"enum_ranges":
    "Contract": [
        "Status": 4,
    ]

If user already uses prettier we should use:

• user installed prettier version
• user defined config (.prettierrc / package.json config)

This way we ensure that typechain generated code matches style with the rest of the codebase.

Overview

Currently when I run brownie console, it recompiles all the contracts. Apparently due to some issue which is not identified.

I only want to compile once with brownie compile -all. That's it.
I work on the frontend side, I don't modify the contracts, I just need a local fork and run some scripts.

Currently it's slow as hell

Add an example to load file from a directory along with https://remix-ide.readthedocs.io/en/latest/locations.html#load-one-of-the-default-remix-files