Joseph Ferano
2e203f64b8
The INSERTIONSORT crash, all three rulings (FIX.org 2026-09-20): - (bytes s) allocates a writable copy through the allocator surface — context or (bytes s a), StorageExhausted with retry, a registry note in dev builds (flan_bytes_dup, lowered like vec-new). (bytes-view s) is the old zero-cost reinterpret, renamed, read-only by convention; every in-repo reader swept over to it. (string b) unchanged. - String constants were already read-only on both backends at -O0; now pinned — bytes-copy.flan rows on LLVM/-O0/--x86, and dies_segv rows asserting the write-through-view trap on both backends. - A dev build installs a SIGSEGV/SIGBUS handler by the same dev-only constructor slot that arms the registry: one line naming the address and the innermost frame, then the trap-hook park — stopped, not dead, the daemon serving. No agent: message and re-raise. Release builds untouched. Pinned by trap_park over dev-segv.flan.
22 lines
775 B
Plaintext
22 lines
775 B
Plaintext
;;;; Value semantics, spec-memory.md. Not covered by calc-me, and the property
|
|
;;;; most likely to be silently wrong in a backend: a struct or a fixed array
|
|
;;;; copies on assignment, a slice copies only its view.
|
|
(defstruct P [x i32])
|
|
(defvar arr [3 i32])
|
|
|
|
(defn main [] i32
|
|
(let [a (P {.x 1})]
|
|
(let [b a] ; a copy, not an alias
|
|
(set (.x a) 99)
|
|
(print (.x b)) (println ""))) ; 1
|
|
|
|
(set (at arr 0) 5)
|
|
(let [c arr] ; fixed arrays are values too
|
|
(set (at arr 0) 77)
|
|
(print (at c 0)) (println "")) ; 5
|
|
|
|
(let [s (bytes-view "hello")]
|
|
(let [v (slice s 1 3)] ; a view into the same bytes
|
|
(print v) (println ""))) ; el
|
|
0)
|