Joseph Ferano
d6fc15474b
The author: "I think I prefer length over len, because then I'll use len as the variable name". One arm in check.ml, one row in the table beside it, and every (len x) in lib, test, examples, vendor, spike, docs, web, emacs, plan.org and NEXT.md rewritten. Shadowing and builtin/ had already taken most of the sting out: a (defn len ...) was legal and won in its own file, and builtin/len reached past it. What was left is that len was still a builtin — the defn earned a warning, and a wrapper had to say builtin/ at every inner call. Now there is nothing under the short name: len is an ordinary identifier in every position, which is what (let [len (length xs)] ...) wants. length takes over as shadowing's worked example rather than the feature losing one. shadow-builtin.flan, builtin-qualified.flan, pkgs/shadowed and the builtin/ rows in test_flan move to it and go on testing shadowing. A call to a len nothing defines is answered where an unknown function is, after every table and after the shadowing guard, so a program with its own len never reaches it. The sentence is said rather than guessed at — len and length are three edits apart and the did-you-mean's net is one — and the call is written back out through spell_arg, as-slice's spelling lifted out of it and now shared, so what is printed compiles. sand.flan:33 still calls the old name and is the author's to change; until it does, test_acceptance and test_session abort there. Both were run green against a copy with that one line changed. FIX.org says so.
54 lines
2.2 KiB
Plaintext
54 lines
2.2 KiB
Plaintext
;;;; defjson over a config file, and the escape that says it is not defedn.
|
|
;;;;
|
|
;;;; The same idea as edn-provide.flan and a different package: json depends on
|
|
;;;; edn for nothing and this program imports only json.
|
|
;;;;
|
|
;;;; "name" is the line that matters. Its value in the file is written
|
|
;;;; "tileset\nrunner", and JSON's `.text` is the RAW interior — escapes
|
|
;;;; undecoded — so a reader built on `.text` prints one line with a backslash
|
|
;;;; and an n in it. This prints two lines, which is `string-of` having been
|
|
;;;; used where a field is filled.
|
|
|
|
(import json "vendor:json")
|
|
|
|
(json/defjson Config "assets/json/config.json")
|
|
|
|
(defconst config (embed "assets/json/config.json"))
|
|
|
|
(defn main [] i32
|
|
(let [a (heap-allocator)
|
|
cfg (Config-of-bytes config a)]
|
|
;; Two lines, not one with a backslash in it.
|
|
(println (.name cfg))
|
|
(println (.port cfg))
|
|
(println (.scale cfg))
|
|
(println (if (.debug cfg) "yes" "no"))
|
|
(println (length (.layers cfg)))
|
|
;; 3 + 1 + 4 + 1 + 5. A length alone would pass on a Vec that was allocated
|
|
;; and never filled, so the sum is the claim.
|
|
(let [total (i64 0)]
|
|
(dotimes [i (length (.layers cfg))]
|
|
(set total (+ total (at (.layers cfg) i))))
|
|
(println total))
|
|
;; The nested structs, by the names the paths give them: Config-window and
|
|
;; Config-window-origin. Ordinary field loads, two deep.
|
|
(println (.w (.window cfg)))
|
|
(println (.h (.window cfg)))
|
|
(println (.x (.origin (.window cfg))))
|
|
(println (.y (.origin (.window cfg))))
|
|
(println "")
|
|
;; Drift, the same contract defedn's reader carries: the struct says "port"
|
|
;; and these bytes do not, and they carry a "host" it has never heard of.
|
|
(handler-bind
|
|
[(json/SchemaDrift [d]
|
|
(do (print (if (.extra? d) "extra " "missing "))
|
|
(print (.field d))
|
|
(print " in ")
|
|
(println (.struct d))))]
|
|
(let [c2 (Config-of-bytes
|
|
(bytes-view "{\"name\":\"x\",\"host\":\"h\",\"scale\":2.0,\"debug\":false,\"layers\":[1],\"window\":{\"w\":1,\"h\":1,\"origin\":{\"x\":0,\"y\":0}}}")
|
|
a)]
|
|
(println (.name c2))
|
|
(println (.port c2)))))
|
|
0)
|