@mfikes so I’m working on auto-aliasing of clojure.* namespaces to cljs.*

this means people can write (:require clojure.spec) etc and it will ust work

this relies on some classpath things of course that I don’t have answer for wrt to bootstrap

That makes sense. (There is some precedent in other parts of CloujureScript for doing that sort of thing, I’ve noticed.)

not a huge deal since it’s mostly a convenience thing

but if you have any thoughts here happy to see patches to make the same thing work for bootstrapped

Ahh, so the bootstrapped load function may simply pass ’clojure.spec to the bootstrapped client, unless something else is done. Yeah, I think I see where you are going.

@mfikes: the problem is that currently the resolution bit is just simpler to do directly in the compiler and conditionalize it

but I don’t have answer for how it should work in bootstrapped

@dnolen: Cool. Looking forward to seeing what you produce for JVM ClojureScript as inspiration for ideas on how that might lead to stuff for bootstrapped.

@dnolen: namespaced-map support to tools.reader is almost ready, release should be by tomorrow. I'm using cljs.analyzer/*cljs-ns* to resolve namespaces for #::foo{}, is that ok?

@bronsa yes

and great!

gah, don't think I can use *cljs-ns* actually as that doesn't exist at runtime

might have to add a *ns* var to cljs tools.reader

nevermind, I brainfarted. cljs has a *ns* so that should be fine

@dnolen: *ns* seems to be nil in a cljs repl, is that a bug?

no

there’s no such thing as actual runtime *ns*

but I don’t see why you need this anyway

how is this different from ::foo

might be missing something

no it's the same as ::foo, they both use *ns*. I must've forgot that the cljs version of tools.reader needs users to bind it then

both cljs & bootstrapped cljs are going to work fine as they bind *ns* while reading AFAICT tho

ClojureScript analyzer binds *ns* when reading yes

and so does bootstrapped

that'll do fine then 👍

Thanks @bronsa for zero-latency-turnaround on this 🙂 Woot!

@bronsa yes, big thanks!!

the clj[s] version was surprisingly (? :)) simple compared to the java one

good!

~20 lines + a helper function, maybe 35/40 in total

@bronsa: cool, are you cutting a release today?

just cut 1.0.0-beta3

I'll probably cut 1.0.0 next if no issues come up

excellent

@bronsa Found an issue in bootstrap. This works but with a warning. Will write up a ticket:

cljs.user=> #::{:foo 1}
null is not an object (evaluating 'ns_obj.name')
{:cljs.user/foo 1}

https://github.com/clojure/clojurescript/commit/783001a6786f8dca4a13fdeadc995716903b07f9

Wow!!!

does this mean the end of :refer-macros?

@cfleming: A new thing to update Cursive for ^

@anmonteiro: yes if the macro ns and the runtime ns share the same name

we’ll sort it out for you

yeah, that requirement makes sense

awesome stuff!