Solidity

Original title: "unusual behavior with mapping within struct within library".

Description

When a library contains a struct type whose only member is a mapping, and a contract contains a public member of that struct type, then compilation fails with error Internal or recursive type is not allowed for public state variables.. But if you add a further field in the struct (of type `

When using the --quiet option with the migrate command, Truffle displays the "possible unsupported option" message. This should be added into the allowedGlobalOptions array for the command so that it doesn't display this message.

Description
Add a contract similar to Aave's AddressProvider or Uniswap's getPair() functionality.

Motivation
On-chain lookups of price oracles given the asset addresses.

Justification
String manipulation is difficult and expensive in Solidity, and you usually work with the token address, not its string name.

Testing methods like evm_mine and evm_increaseTime expect integer parameters. Unlike other methods, they reject these parameters if they are not decimal-encoded.

To reproduce

npx hardhat --version -> 2.5.0

Run npx hardhat node and make the following rpc calls:

> curl -H "Content-Type: application/json" -X POST --data \
        '{"id":1337,"jsonrpc":"2.0","method":"evm

Add flags to slither-check-upgradeability to disable some detectors per name, or per detectors impact, or to enable only some of the detectors (per name/impact)

We should add explicit runtime errors that stop CLI execution when an obvious version mismatch is detected. No one (me neither) checks peer dependency-related errors from a package manager.

TC should bail if:

• ether target has detected too low ethers version detected
• tc core package is too low to support given target package

Each target package should be able to define custom conditions

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

We can safely disallow any use of solc below 0.4.25.

Originally reported in ethereum/solc-bin#21 (comment).

soljson-v0.4.1-nightly.2016.9.9+commit.79867f49.js crashes solc-js because the version it reports apparently does not conform to semver. solc-js should be able to handle that more gracefully.

This happens for --version and --bin. Probably in other cases too.

Repro

npm install sol