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.
18 lines
755 B
Plaintext
18 lines
755 B
Plaintext
;;;; The reserved qualifier, from the import's side. Refused, never built.
|
|
;;;;
|
|
;;;; builtin/length means the compiler's length and must go on meaning it,
|
|
;;;; which is
|
|
;;;; only true while nothing else can produce the qualifier "builtin". Every
|
|
;;;; qualifier in a finished program comes from an import's alias, so refusing
|
|
;;;; that one alias is the whole of the reservation — there is no other door.
|
|
;;;;
|
|
;;;; It is the alias that is reserved and not the directory: the package this
|
|
;;;; names is imported under its own alias by shadow-builtin.flan and is fine
|
|
;;;; there. The importer chooses the qualifier, so the importer is where the
|
|
;;;; collision is.
|
|
|
|
(import builtin "pkgs/shadowed")
|
|
|
|
(defn main [] ()
|
|
(println (builtin/field {:a 1 :b 4})))
|