This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-10
Channels
- # announcements (9)
- # babashka (19)
- # beginners (39)
- # calva (7)
- # cherry (1)
- # cider (2)
- # clojure (31)
- # clojure-europe (8)
- # clojure-norway (9)
- # datalevin (10)
- # events (2)
- # fulcro (10)
- # hyperfiddle (9)
- # joker (1)
- # lsp (50)
- # membrane (34)
- # minecraft (2)
- # missionary (21)
- # off-topic (17)
- # pedestal (1)
- # polylith (8)
- # reitit (3)
- # sql (4)
- # squint (16)
- # xtdb (14)
Haven’t had a chance to look at this until today when noticed the name change posted on Twitter. It reminds me very much of Fennel, which compiles to Lua (which I use to configure Neovim)!
that came up when we were discussing a new name
fennel is pretty nice 🙂
in squint is nthnext just:
export function nthnext(xs, n) {
return seq(xs) ? drop(n, xs) : null;
}
or do we want to eagerly realize that into an array?
or do we want to eagerly realize the iterator and then put the remaining values back into a new instance of the type that xs came in as?
user=> (nthnext {:foo "bar" :baz "qux" :hi "bye"} 1)
([:baz "qux"] [:hi "bye"])
seems like we could just convert it to a vec and return it?
I have come to think maybe we don't need to include nthrest/next since they would just be equivalent to drop
cc @U4YGF4NGM for second opinion
What inspired the name change?