This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-09
Channels
- # admin-announcements (1)
- # boot (225)
- # braid-chat (1)
- # cider (25)
- # cljs-dev (35)
- # cljsrn (1)
- # clojars (6)
- # clojure (81)
- # clojure-berlin (1)
- # clojure-dev (21)
- # clojure-france (2)
- # clojure-japan (6)
- # clojure-poland (1)
- # clojure-russia (10)
- # clojure-uk (3)
- # clojurescript (121)
- # code-reviews (1)
- # core-async (4)
- # core-logic (2)
- # cursive (15)
- # datomic (8)
- # hoplon (4)
- # jaunt (112)
- # jobs-discuss (35)
- # om (41)
- # parinfer (8)
- # re-frame (3)
- # reagent (4)
- # ring (2)
- # untangled (38)
I’m trying to run #C0F4MB8AY on #C0SBWN3AP. I’m getting a lot of warnings, which is cool. I’m also getting an error from prismatic.schema that clojure.core/refer* is not public.
Also, I had to upgrade my JDK and unset my JAVA_HOME to run it. Apparently I was pinned to Java 7
@eraserhd: :refer-clojure
in a ns form will work just fine. Are you seeing a (refer-clojure ...)
at the top level of a file?
I did a quick grep, and didn't see anything weird, but I could have missed something. Jaunt is smarter about NS forms?
Okay. That's what I'm patching right now. I'll have a 0.3.0-SNAPSHOT build for you in a sec.
midje has a lot of deprecation warnings. I will submit a PR later. (all about ‘:use’)
The fn metadata stuff bronsa was helping me with was the main blocker to getting that out the door. Should happen this week.
Oh, I read your whole blogpost last night. Oxcart is so what I would do, had I time.
In fact, Clojure was the last Lisp to study before making Moreso, and it kind of broke me.
I feel like something like oxcart would be better off as a language started off from scratch rather than piling stuff on top of clojure
Yeah. Oxcart was a bunch of fun. We'll see how much of that and the strict clojure stuff I did with amalloy makes it into Jaunt.
Definitely agree wrt starting from scratch, but Jaunt is an exercise in avoiding those reinvention costs.
btw @arrdem I was talking about oxcart/kiss at clojurex with @mtrimpe -- the "def as pure action over an immutable ns" thing has some non-trivial obstacles to overcome
I spent a lot of time last year sketching out how to make def a fn from an env and an expr to an ev.
I think a clojure-y language would gain a lot more by having racket-style compilation stages than immutable namespaces
I think that the ns reloading changes I've got coming down the pipe address the primary shortcomings of the existing mutable nss.
here's some context though https://docs.racket-lang.org/guide/phases.html#(tech._phase._level)
@bronsa: I discovered that Clojure can't/won't emit an invokePrim call for a lambda because it uses arglist var metadata to find the prim hint 😕
I've been pondering whether it makes sense for defn to put metadata on the var. For instance doc metadata would arguably be more useful on the fn.
@bronsa: so I had this idea today... #:foo {:unqual 0 ::bar 1 ::baz/qux 2 'unqual 3 '/qual 4 '/alias/qual 5}
the idea is just that you define /
as a symbol prefix to mean contextual qualification same as ::
on keywords does.
I understand that Rich considers it a syntax bikeshed, but I agree with you about : vs :: and think it's a critical one.
kinda hard to gauge if the syntactic tradeoffs being proposed are worth it without them giving us the full context
happy to at least know that macro grammars in some form or the other are likely coming in 1.9
I don’t think I’ve needed anything like this. Though I guess I understand the semantic thing.