Joseph Ferano
96ab4c9cf0
print-str, print-i64, print-f64, print-bytes, print-line and newline leave the prelude. print and println are the whole printing surface now, and print is the better call at every one of the sites that used them: it is the same structural walk without the newline, so the no-newline case the family was kept for is covered, and it takes the value as it is. The old print-i64 forced an explicit (i64 x) at every call site, because this language widens nothing implicitly; that cast is gone from 127 places. Dropping it moves one answer. hash-grid returns u64, and the cast through the signed printer showed sand-headless's hash as -2851001042534928384. print routes a u64 through flan_u64_to_bytes, so it now prints 15595743031174623232 — the same 64 bits, read as the unsigned number they are. The pinned expectation follows the correction. test-flan-dev.el and test_session.ml both reached for print-line as "a name the prelude has"; they reach for rand-seed instead.
25 lines
820 B
Plaintext
25 lines
820 B
Plaintext
;;;; v4 redefines only [added] — itself introduced at run time by v3, so it
|
|
;;;; lives in the registry and not in any symbol table.
|
|
;;;;
|
|
;;;; This is the case that separates a real implementation from a plausible
|
|
;;;; one. v3's [bump] is already installed and is not rebuilt here, so it picks
|
|
;;;; this up only if its call to [added] goes through a *cell* that both
|
|
;;;; modules found by name. Had v3 cached the address of the function instead
|
|
;;;; of the address of its cell, everything else would still pass and this
|
|
;;;; would silently keep running v3's [added].
|
|
(defvar counter i64)
|
|
(defvar extra i64)
|
|
|
|
(defn helper [x i64] i64 (* x 2))
|
|
|
|
(defn added [] i64
|
|
(set extra (+ extra 100))
|
|
extra)
|
|
|
|
(defn bump [] i64
|
|
(println "v3")
|
|
(set counter (+ counter (added)))
|
|
(helper counter))
|
|
|
|
(defn outer [] i64 (bump))
|