plan.org now says every Flan function carries the transfer channel, that uniformity is what keeps indirect calls and hot reload ABI-safe, and that a later optimisation cannot change the ABI. spec-conditions.md §6 still read the other way round - escape analysis deciding which functions are transfer-transparent, with the rest paying nothing - which describes a signature that depends on an analysis, and a cell cannot hold one of those. So the analysis is demoted to what it can still honestly do: a function that provably cannot transfer need not check the channel after a call and can pass the pointer straight through. It may not drop the parameter. NEXT.md said the same thing as a for-later note and now says it is settled.
Description
Languages
OCaml
67.2%
Emacs Lisp
15.2%
C
10.4%
HTML
2.9%
Standard ML
2.8%
Other
1.5%