This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-15
Channels
- # admin-announcements (7)
- # alda (1)
- # aws-lambda (1)
- # beginners (12)
- # boot (20)
- # cider (59)
- # cljs-dev (4)
- # cljsrn (69)
- # clojure (232)
- # clojure-austin (3)
- # clojure-austria (1)
- # clojure-belgium (2)
- # clojure-canada (3)
- # clojure-dev (16)
- # clojure-greece (33)
- # clojure-nl (4)
- # clojure-quebec (12)
- # clojure-russia (12)
- # clojure-spec (27)
- # clojure-uk (38)
- # clojurescript (29)
- # community-development (7)
- # component (53)
- # core-async (16)
- # core-logic (1)
- # datascript (7)
- # datomic (11)
- # editors (7)
- # emacs (69)
- # hoplon (157)
- # keechma (1)
- # lambdaisland (2)
- # lein-figwheel (31)
- # leiningen (8)
- # mount (3)
- # off-topic (11)
- # om (23)
- # onyx (64)
- # planck (2)
- # re-frame (18)
- # reagent (21)
- # specter (118)
- # untangled (145)
- # yada (1)
var type hints aren't really deprecated, type hinting the argvec has been the preferrable way of type hinting for a while
@alexmiller: any reason I'm missing why vectors are Comparable
but sequences aren't or is it just an oversight?
thought I could write (sort-by (juxt val key) the-map)
as (sort-by rseq the-map)
or (sort-by reverse the-map)
but apparently not
There's a ticket out there re making lists comparable
I guess sequences would be similar
I'm not sure though if there is some reason why they aren't already
The vector behavior is specifically doc'ed on the data structures ref page so it seems like it was a conscious choice
But can't say I know why
@alexmiller: @bronsa maybe they're not comparable because of lazyness? Aka, compare would force to evaluate the whole sequence. Not saying they should not be, but that could point why they aren't yet