This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-14
Channels
- # aatree (1)
- # admin-announcements (1)
- # beginners (12)
- # boot (359)
- # cljs-dev (23)
- # cljsjs (2)
- # cljsrn (1)
- # clojure (53)
- # clojure-czech (5)
- # clojure-madison (1)
- # clojure-russia (15)
- # clojured (8)
- # clojurescript (16)
- # community-development (2)
- # core-async (6)
- # cursive (19)
- # datomic (31)
- # emacs (48)
- # euroclojure (3)
- # hoplon (29)
- # microservices (7)
- # mount (46)
- # off-topic (7)
- # om (11)
- # proton (74)
- # reagent (4)
- # spacemacs (3)
Hah, the compiler is starting to feel slightly sentient:
WARNING: Unknown compiler option ':optimisations'. Did you mean ':optimizations'?
WARNING: Unknown compiler option ':bogus'.
WARNING: Unknown compiler option ':mein'. Did you mean ':main'?
WARNING: Unknown compiler option ':input-to'. Did you mean ':output-to'?
WARNING: Unknown compiler option ':argit'. Did you mean ':target'?
WARNING: Unknown compiler option ':outputdie'. Did you mean ':output-dir'?
Lol nice
Did you use some kind of clever diff?
@richiardiandrea: It finds a key with minimal Levenshtein distance from the mis-typed key.
Ahaha great job!
@dnolen: done, patch included: http://dev.clojure.org/jira/browse/CLJS-1568
still on the topic of metadata in collections: this is possible in clojure:
user=> (meta (with-meta (seq [1 2 3]) {:a 1}))
{:a 1}
while in CLJS:
cljs.user=> (meta (with-meta (seq [1 2 3]) {:a 1}))
No protocol method IWithMeta.-with-meta defined for type cljs.core/IndexedSeq: (1 2 3)
cljs$core$missing_protocol (cljs/core.cljs:264:4)
cljs$core$_with_meta (cljs/core.cljs:570:1)
cljs$core$with_meta (cljs/core.cljs:1845:8)
also an oversight or expected?
@anmonteiro: definitely an oversight
@dnolen: OK, will open issue
btw, I commented on CLJS-744 but I'll ask here anyway. Is is alright if I assign it to myself?
@anmonteiro: yes always OK to assign to yourself if you’re going to take it
@dnolen: cool, thanks. it's the one about indexOf
and lastIndexOf
in ISequential
.
I'm thinking that the way to approach it is to (specify! ISequential Object ...)
, is this the wrong way to look at it?
@anmonteiro: I would just add the Object methods, I wouldn’t bother with specify
@dnolen: I have some doubts regarding CLJS-744.
It seems that in some cases (e.g. IndexedSeq
) we could delegate to the native host .indexOf
but in others (e.g. RSeq
) this would not be possible
@anmonteiro: equality semantics are different
oh that's right
custom implementation it is
it actually makes things easier