This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-10-09
Channels
- # admin-announcements (9)
- # boot (114)
- # cider (15)
- # cljs-dev (10)
- # clojure (35)
- # clojure-boston (5)
- # clojure-dev (39)
- # clojure-greece (1)
- # clojure-japan (10)
- # clojure-nl (3)
- # clojure-poland (2)
- # clojure-russia (10)
- # clojure-sg (8)
- # clojure-switzerland (1)
- # clojure-uk (34)
- # clojurescript (76)
- # clojurescript-ios (3)
- # clojurewerkz (1)
- # clojurex (9)
- # cursive (3)
- # datomic (1)
- # devcards (137)
- # emacs (5)
- # events (1)
- # hoplon (99)
- # jobs (1)
- # ldnclj (50)
- # off-topic (1)
- # om (3)
- # onyx (10)
- # re-frame (4)
- # reagent (1)
- # ring-swagger (15)
- # yada (35)
@alexmiller: I just realized I didn't document the new :load-ns opt to deftype/defrecord in my patch for CLj-1208
you mean docstring?
new ticket - I will just pull it up into 1.8 as that seems important
I'd also welcome a para for the http://clojure.org/datatypes page too
ok -- I'm not on my dev laptop rn so I can't make a patch, I'll just open a ticket and handle that tomorrow
@alexmiller: CLJ-1823
Hi, there. Is it known/okay that &
gets silently bound in this case:
(defprotocol Foo
(foo [this & b]))
=> Foo
(deftype T []
Foo
(foo [o & b] [o & b]))
=> user.T
(foo (->T) 1 2)
=> [#object[user.T 0x7e01f15e "[email protected]"] 1 2]
Working on warning the user cljs-side http://dev.clojure.org/jira/browse/CLJS-1445There is a clj ticket for this too
It is known and not ok imo :)
@alexmiller: can you close CLJ-1773? (it's just marked as resolved)
@alexmiller: will search for the ticket, thanks. BTW, I don't get why it'd be bad to be able to have variadics in protocols (one day)?
protocols create Java interfaces as well as Clojure functions and that creates some complications
potentially resolvable complications
it comes up occasionally
http://dev.clojure.org/jira/browse/CLJ-1661 is one of the & protocol tickets
http://dev.clojure.org/jira/browse/CLJ-1024 is another, seems like they are dupes
I guess 1661 is the one. there's some weird history some of which is on the mailing list. I marked it triaged but that ticket needs some work though.
It is not evident if someone is onto it, I'll be checking maybe, missing Java a bit ^^
the ticket description needs work to better capture the problem and approach
feel free to do so
prob good to check whether the patch still applies too
@alexmiller: tbh I never understood the position clojure has wrt java varargs. there is bytecode annotation for varargs so clojure could handle java varargs automatically rather than as a single arg (and in the same vein, compile vararg protocol methods into java varargs)
I've never talked to Rich about it, but my guess is that all those ends were just never tied down
@bronsa: By the way, what's your status with regard to tools.reader releases? I put the "alpha" label on tools.namespace 0.3.0-alpha1 because it depends on tools.reader 0.10.0-alpha3
@stuartsierra: I just forgot to release 0.10.0
@bronsa: hah! No worries, thanks