users are just going to write (:require [clojure.test :as test :refer […]) and be done with it

@spieden lein deps :tree to make sure you don’t have some weird dep conflicts

(i.e. something is pulling in an older version of ClojureScript)

@dnolen i did indeed, just now got it sorted

then went and read about project jigsaw only to learn they aren’t doing anything for version conflicts in JVM land =\

@spieden we leave the task of automatic conflict resolution to some future alien civilization

@dnolen Ok, thanks - yes, I assumed that was the case. I’ll implement that.

@anmonteiro Thanks!

does ns-resolve exists in clojurescript ?

@lxsameer nope, namespaces are not reified at all - none of that functionality exists

vars also only exist in a highly limited fashion and it’s best to have no expectations

(the story for bootstrapped is different, but I’m assuming you’re not asking about that)

thanks man

@dnolen bootstrapped clojurescript is a different variant of clojurescript, right ?

@lxsameer not really

it’s a provided self-hosted option for people who don’t care about greatly increased code size

and losing advanced compilation entirely

thanks

This may sound stupid but is defmacro in ClojureScript a thing now? I'm looking at spec.cljc in the ClojureScript repo and it has defmacro without a surrounding reader conditional. How does that work?

@jannis it’s meant for self-hosted CLJS

you can read a bit more about that here: http://blog.fikesfarm.com/posts/2015-12-18-clojurescript-macro-tower-and-loop.html

there are some other posts of interest re: macros in that blog too

@jannis not a thing, and isn’t going to be

@anmonteiro, @dnolen: Ok, makes sense

is it expected when a let binding name shadows a js global, the global becomes inaccessible with js/...?

i can see from the generated source why it happens, but it surprised me

@eyelidlessness that is not expected, I would expect js/ to work regardless

to me “js/“ is a view to “Javascript world”, not just a syntactic sugar

(defn simple-repro []
  (let [location (str js/location.pathname)]
    location))

aha, I’m sorry I misunderstood

that looks like a bug to me 🙂

though i'd expect it would not throw with advanced compilation

(this is with whitespace optimization only)

@eyelidlessness not sure what you would expect

since that’s just JS scoping rules

not a bug

like i said, i understood why it happened.

that’s how it works

like i said, i understood why it happened.

more specifically js isn’t a namespace

so there’s no simple way for it to work

it's at least surprising; I also didn't realize that js/window may fail in a let

now you know 🙂

js works a certain way and it’s not going to change

it’s probably simple to warn about the mistake though

:thumbsup:

and anyone can submit a patch for that

a warning would go 95% of the way of removing the surprise yes!

a relatively simple change for somebody who wants to contribute

I’m not going to spend any time on it except reviewing a patch

makes sense. i may take a look at it.

agree makese sense

if you want to get involved jump on #cljs-dev and ask questions

thanks @dnolen

a few people understand how warnings works, and how we could check js/foo conflict with a local

related: http://dev.clojure.org/jira/browse/CLJS-833

i'm gonna take some time looking through the codebase and see if i can't grok how to do it, before i ask any questions.

@pesterhazy yes it’s the same problem - but wasn’t interested in the proposed solution

a warning suffices

i agree. i would prefer less name mangling, not more 🙂

cljs.analyzer/resolve-var is probably the place for the fix

some care must be taken to handle cases like js/window.location

@eyelidlessness @pesterhazy feel free to open a minor enhancement ticket in JIRA

looks like there's some special casing already for some common globals: https://github.com/clojure/clojurescript/blob/92459050162fce53312d9df7d7b5c703d2d992c2/src/main/clojure/cljs/analyzer.cljc#L585

something like a “warning for shadowed js/foo"

@pesterhazy yes but unrelated to this enhancement

one minute (eternity) while i relearn how to use jira

http://dev.clojure.org/jira/browse/CLJS-1785

wouldn't throwing an error be even better than a warning? Is there any situation where you want to use js/location to refer to a let binding?

just a thought

makes sense to me.

I added a bunch of newbie friendly tasks today http://dev.clojure.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10616

almost all of them are trivial clojure.spec stuff

bbiab

@pesterhazy no

plus warnings are customizable

if you want your own build to fail - go for it

@pat doc is in clojure.repl namespace. So either (use 'clojure.repl) and (doc map) or (clojure.repl/map) ps. use wont work with cljs, but if you are using cider, then most likely you have clj repl at hand.

@hlolli that pin was my clumsy thumbs scrolling on the train, my apologies for the noise

anyone would like to share if they’ve done projects involving arduino/raspberry-pi with clojurescript? I want to gauge what the possibilities are