Joseph Ferano
4cb53a0a9f
The four refusals the function-value lane wrote down are now three and a half: capture is a feature, the escape is the refusal in its place, and a struct field or a global of function type is refused for the same zero as before with a sharper reason behind it. The handler note is amended rather than deleted -- its reading was right, and saying so is worth more than a clean paragraph. The convention section carries both rulings, the name and every name it beat, the warning that CFn is not C interop today, the four reasons to reach for it, what was measured rather than asserted about an ordinary defn, and the wasm32 finding that killed the first design -- being exactly typed is checkable by a verifier and the alternative was an argument from a calling convention. FIX.org carries the rulings verbatim, what the escaping lane inherits and changes, the thunk's environment holding a code pointer rather than a GC object, and two things recorded and not built: a CFn under a future --no-conditions reaching C's exact convention, and CFn in a struct or a fixed array, which ZII refuses and capture has nothing to do with.