docs: partition-all letfn is for minimal realization, not jolt-zxw
jolt-zxw (multi-arity arity-param mis-capture in a nested lazy-seq under :compile?) is no longer reproducible: an arity-direct partition-all now compiles correctly in the overlay. The original failure was an artifact of the CLJ multi-arity version coexisting with the Janet core-partition-all ([n & rest]) during migration — the shadowing confused multi-arity dispatch; removing the Janet version resolved it. The letfn in partition-all stays purely for minimal realization (jolt-yo3).
This commit is contained in:
parent
df59a04b83
commit
3da5a5fcfa
1 changed files with 3 additions and 4 deletions
|
|
@ -104,10 +104,9 @@
|
|||
|
||||
;; --- partition-all --- (transducer + [n coll] + [n step coll])
|
||||
;; The collection arities realize EXACTLY n per chunk via a first/rest loop and
|
||||
;; continue from the advanced cursor (not a re-drop), so they realize minimally
|
||||
;; — matching the Janet pstep the §6.3 laziness counters were written against.
|
||||
;; letfn-bound `go` (not arity-direct recursion) sidesteps the compile-mode
|
||||
;; multi-arity closure-capture bug (jolt-zxw), as keep-indexed/map-indexed do.
|
||||
;; continue from the advanced cursor (not a re-drop / nthrest), so they realize
|
||||
;; minimally — matching the Janet pstep the §6.3 laziness counters were written
|
||||
;; against. (A take/nthrest form is correct but over-realizes.)
|
||||
(defn partition-all
|
||||
([n]
|
||||
(fn [rf]
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue