Ethereum

System information

Geth
Version: 1.10.13-stable
Git Commit: 7a0c19f813e285516f4b525305fd73b625d2dec8
Architecture: amd64
Go Version: go1.17.3
Operating System: linux
GOPATH=
GOROOT=go

Expected behaviour

Close files that aren't in use / have a settable limit

Actual behaviour

Every database file it opens stays open for the duration of the sync

Steps to re

🧐 Motivation
Solidity 0.8.13 marked the production readiness of the Yul IR pipeline. This, amongst other things, helps to alleviate stack too deep errors by allowing the compiler to move items to memory as and when needed.

📝 Details
One requirement of the pipeline is that any assembly sections be memory-safe, such that they only use memory that has been previously allocated either by

Should be done after #12934.

Page

• Cheatsheet

Abstract

When we're done cleaning up the cheatsheet, we could add more interesting information that's already described elsewhere but less concisely. Some ideas:

• Table of available types.
• Various types of literals (in particular string literals like

Issue

Vyper handles unmapped instructions differently from Solidity. In Solidity, unmapped instructions are given a file index of -1. When attempting to show the source for such an instruction, we instead just show 1: // No source code found..

However, in Vyper, such instructions are not given a file index of -1, but are given a start and length of 0. So when we show the source for t

A parametrized option to set the blocksize would be useful to experiment with. As quorum is used in a private setting I think this option should be available