Radar · Solidity · Archive · Week 18 · Apr 27 – May 3, 2026

Keyword promotion warnings for Yul identifiers

Worth knowinglanguage

What changed: Yul analysis now warns about identifiers that may be promoted to Yul keywords or reserved (basefee, blobbasefee, blobhash, clz, leave, memoryguard, mcopy, prevrandao, tload, tstore).
Production impact: The source does not say.
Try it: Write a Yul snippet using tstore and check the warning.
Source: github.com/argotorg/solidity/releases/tag/v0.8.35

Understand it, then run it

Solidity 0.8.35 adds a new warning that tells you when you use an identifier that could become a keyword in Yul in the future. If you write an assembly block that contains a variable or function name like leave, memoryguard, or tstore, the compiler will emit a warning. The warning does not change how the code runs; it only alerts you that the name might clash with a future keyword. This helps you avoid accidental name collisions when Yul evolves.

Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed