wurstscript / WurstScript / 40141698262

80%

push

github

Lua hot reload: materialize new compile-time object snapshots (#1563)

* Lua hot reload: a closure inserted before others of its order group reloads

The build still names the closures of an order group by their position. The payload, made for the running map,
matches the edit's closures with those the map has (by source, against what the last payload sent) and gives each
name the class table and captured-value stores of the closure it continues, so objects made before keep their
closure and values. An insertion and an edit before the same unchanged closure cannot be told apart and are refused.

* Lua hot reload: removed closures of an order group apply while no other takes their names

Removing a whole group of declarations which share an identity left nothing to confuse but was refused; the
closures of a group are now decided by their lineages, so removing the last ones (or all) applies with the
warning of a removed function, and a closure added later in a removed one's names is refused unless it is
that one back. Castle Fight replay and the remaining refusals in docs/LUA_HOT_RELOAD.md and BACKLOG.md.

* WIP: Lua hot reload: name compile-time objects after what made them

Work in progress, not compiled or tested after the last edits. Adds failing
repro tests (an added compile-time object is nil after a reload; one inserted
above another takes its object; removing one is refused with the closure-order
message), and gives each compile-time object and hashtable global an identity
from the value it was computed for and the path through it. The payload side
(initCompiletimeState as manifest statements) is not done; see the PR.

* Reserve removed callback lineages and retain empty layouts

* Replay new compile-time objects before hot reload initializers

* Preserve bound compile-time identities and traced replay ownership

* Protect removed capture names when a surviving closure moves

* Guard materialized compile-time expression groups across payload his... (continued)

22889 of 30207 branches covered (75.77%)

Branch coverage included in aggregate %.

42212 of 51488 relevant lines covered (81.98%)

4.12 hits per line