This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-04
Channels
- # aleph (10)
- # announcements (2)
- # babashka (2)
- # beginners (101)
- # calva (17)
- # cider (11)
- # clara (6)
- # clj-kondo (25)
- # cljsrn (33)
- # clojure (181)
- # clojure-dev (15)
- # clojure-europe (3)
- # clojure-italy (4)
- # clojure-nl (8)
- # clojure-uk (22)
- # clojurescript (111)
- # clojutre (58)
- # cursive (31)
- # data-science (1)
- # datomic (10)
- # emacs (6)
- # ethereum (1)
- # fulcro (20)
- # graalvm (3)
- # jackdaw (5)
- # leiningen (5)
- # off-topic (31)
- # re-frame (2)
- # reitit (10)
- # shadow-cljs (9)
- # spacemacs (16)
- # sql (8)
- # tools-deps (16)
- # vim (17)
I added some more text at the beginning of core.rrb-vector's README explaining in what situations someone may want to use it. Feedback welcome if you give it a read and it seems off somehow: https://github.com/clojure/core.rrb-vector
The original documentation by Michal 🙂
Seriously, I do not know.
i haven't seen the previous version but this is quite nice in explaining rationale, etc
I did recall there was someone commenting on it, but not who. Glad the changes worked for you. I looked at it and realized it was previously written from the perspective of one who knew Clojure internals fairly well already.
I asked as well, to see whether it would be useful for anything at work (it wouldn't, it seems).
So, yes, thank you for the clarification @U0CMVHBL2 !
Sure, its use cases are fairly limited. If my plans for world domination come to fruition, I hope to make it even faster than Clojure's built in vector data structure. But that is a big question mark, and a fair chunk of work away from now.
would love a #hacktoberfest on a data structures type project in contrib with an active maintainer 🙂
I'm not sure what is involved there, but the weird thing is that anything that isn't already fixed, is also on the edge of what I know how to do.