Joseph Ferano
57fe91f303
FIX.org, NEXT.md, DISCUSS.org, docs/DISCUSS.md and the session handoff at the root are one TODO.org now: 293 entries under seven subsystem headings, each carrying an org keyword that says where it stands. A DONE entry is a few lines saying what was decided and what that rules out; the reasoning that would not compress — the embedding spike and the four reports the hand-written x86 backend was built from — moved into docs/BUILT.md instead, and its entries point there in one line. Every entry was checked against the tree before it got a keyword, and the prose was wrong in both directions. Things the deleted files called open were built: the first-evaluation stall, main being redefinable, macro parameter lists, the type-limit constants, the array constructors, the byte fills, inc/dec, the discard's fontification, the Emacs buffers, rt_die's _exit, the backtrace surface, and the acceptance failure that could print and still exit zero. Things they called done were not: the backend reports' no-plan buckets had gone stale in the other direction, the value-dependent defvar was superseded rather than built, and macro-expansion source locations are on an unmerged lane, so that entry is NEXT and names the branch. Every comment that cited one of the five by name now cites a heading that exists, in TODO.org or in docs/BUILT.md. The session reports under docs/handoffs/ keep naming the files they worked on, because rewriting them would falsify what those sessions did; each carries a note saying where the content went.
21 lines
1.2 KiB
Plaintext
21 lines
1.2 KiB
Plaintext
;; ZII fills an omitted field with all-bytes-zero, and a zeroed function value
|
|
;; is a null pointer — the one kind of zero that is not a value the type can
|
|
;; have. Every other type's zero is one: 0, false, an empty slice, None, a
|
|
;; union's first case. So it is refused where the field is written rather than
|
|
;; left to crash at the call, and the same rule covers a global, a fixed
|
|
;; array's element and (zeroed).
|
|
;;
|
|
;; Capture sharpened the reason behind this one without changing it. A struct
|
|
;; outlives the frame it was built on, so a field could not hold a value
|
|
;; carrying an environment either — see fn-escape-*.flan. The zero is still
|
|
;; what the message names, because it is the objection that applies to every
|
|
;; function value and not only to a capturing one.
|
|
;;
|
|
;; Which means a (CFn ...) field is refused too, and for the zero alone —
|
|
;; a table of function pointers is exactly what that type is for, and nothing
|
|
;; about capture stands in its way. An (Option (CFn ...)) field is already
|
|
;; legal and is the shape that works; TODO.org, "CFn in a struct or a fixed array", carries the rest as its own item.
|
|
(defstruct Ops [run (Fn [i32] i32)])
|
|
|
|
(defn main [] i32 0)
|