prxnvt 2d56f1b936 Engine: a macro's check for writes over data keeps a Python cell ...

The footprint dry run and the per-step guard of macro runs (new on main)
compared formulas and values only. A step that replaced a Python cell with
its own cached value, or with other code that also shows #BLOCKED!, was not
counted as a write over data, so the code could be lost without the
question. A step that only blocked a Python cell's spill, which leaves its
code as it was, was counted as one. Python code is now content as a formula
is: a change of code or return type is a write, and a change of the cached
value alone is a recalculation.

2026-11-01 12:09:50 -05:00

..

examples

fix: satisfy stricter clippy lints CI's newer stable toolchain catches

2026-10-12 02:52:07 +02:00

src

Engine: a macro's check for writes over data keeps a Python cell

2026-11-01 12:09:50 -05:00

tests/it

Merge main into Python cells as data

2026-11-01 12:00:09 -05:00

Cargo.toml

Enforce workspace Clippy standards and document lint policy

2026-10-28 10:52:53 +00:00