prxnvt e8f2becf4a Engine: a deleted reference drops a Python cell's kept result; spills read past the scan budget stay values ...

A structural edit that deleted the data an xl() reference names rewrote the
reference to #REF! but kept the cell's cached result, so the cell went on
showing a result for data that is gone. rewrite_python_refs now makes such a
cell new code (#BLOCKED!, no kept result), and the recalculation removes its
spill. A rename or a move, after which the reference names the same data,
still keeps the result.

When the reader's range-scan budget ran out part way through a Python spill,
the rest of its cells were read as plain cells, and the result rebuilt on open
was then blocked by them (#SPILL!). On such a sheet every Python spill now
keeps its values as plain values, with no live spill.

Tests: deleting_the_data_python_code_reads_drops_its_kept_result and
python_spills_read_past_the_scan_budget_keep_their_values_as_plain_values;
both fail without the fix.

2026-11-02 02:27:28 -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 deleted reference drops a Python cell's kept result; spills read past the scan budget stay values

2026-11-02 02:27:28 -05:00

tests/it

Merge origin/main (25881a8e) into the Python cells branch

2026-11-02 01:29:06 -05:00

Cargo.toml

Enforce workspace Clippy standards and document lint policy

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