Joseph Ferano
ea24461107
Two gaps nothing in the suite reached. A dev build, because the hash and equality pair emitted for a struct key is a function nobody wrote, and the only other inhabitant of the lifted list — a handler-bind clause — carries a parent this one cannot: the pair is shared by every function that maps that key type, so it has no single parent. A dev build puts every body behind an indirection cell and is the build that would notice. It does not; maps.flan answers the same nineteen ways at --dev as it does at -O2 and -O0. And a map crossing a function boundary in both directions. Everything else in the file lives and dies inside one let, so nothing would have noticed if the 48-byte header travelled wrongly by value while every runtime operation takes its address. Returning one and passing one are both moves, which is the rule a Vec already follows — verified against a Vec rather than assumed, since a refusal that fired for the wrong reason would look the same. has-key? is flagged in BUILT.md as what it is: an addition, not something spec-memory.md names.
