Makes sense. I just went through the source and it looks like all it does is deref it. So I just replaced it with an atom and passed that in to :hierarchy and it works just fine (even swap!ing it after the defmulti).
Can/Should I rely on this? If not, could this be added as "feature" to the doc string? As far as I can tell :hierarchy is one of the very very few non-dev oriented usages of a #'var. So it would be nice if we could use without getting into the var mess. (I'm planning on using :hierarchy to handle core.async messages where I might want to handle multiple messages with the same handler.) On Monday, April 27, 2015 at 2:32:58 PM UTC-4, David Nolen wrote: > There is no intention to elide this information. static vars are primarily > intended for development and testing - don't use them in production is the > answer for the time being. > > > David > > > On Mon, Apr 27, 2015 at 1:24 PM, AndyR <[email protected]> wrote: > I just messed with multimethods and :hierarchy which expects a var (#' or > var). Doing so emitted my full path name of the cljs file into the JS file > (meta data). Is this on purpose? > > > > Could this be potentially a security issue? > > > > Could we add a compiler option to sanitize this? > > > > Cheers, > > Andy > > > > -- > > Note that posts from new members are moderated - please be patient with your > first post. > > --- > > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > > To post to this group, send email to [email protected]. > > Visit this group at http://groups.google.com/group/clojurescript. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
