This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-19
Channels
- # beginners (37)
- # boot (96)
- # cider (23)
- # clara (2)
- # cljs-dev (40)
- # clojars (1)
- # clojure (149)
- # clojure-conj (1)
- # clojure-dev (2)
- # clojure-dusseldorf (5)
- # clojure-france (82)
- # clojure-italy (1)
- # clojure-nlp (1)
- # clojure-russia (13)
- # clojure-spec (24)
- # clojure-uk (62)
- # clojurescript (131)
- # core-async (13)
- # core-logic (7)
- # data-science (1)
- # datomic (10)
- # defnpodcast (3)
- # docker (4)
- # emacs (3)
- # events (4)
- # hoplon (68)
- # klipse (4)
- # leiningen (1)
- # off-topic (5)
- # om (140)
- # onyx (16)
- # pedestal (24)
- # planck (10)
- # proton (2)
- # re-frame (9)
- # reagent (4)
- # remote-jobs (1)
- # ring-swagger (16)
- # untangled (5)
- # vim (8)
- # yada (30)
Sooo :asset-path
is relative and I can customize it, but what if I want to serve my entire .out
folder from some other place (for dev purposes and to mimic serving assets from somewhere else), how can I do it?
And is this something you would accept a patch for? in boot-reload
there is a :asset-host
key that does kind of that Not true, sorry.
ClojureScript 1.9.293 released https://groups.google.com/forum/#!msg/clojurescript/96RnUYnhq8E/b2TmFNeOCwAJ
@dnolen can you share more details about data literals support and how it relates to the new require
macro?
what files?
@viebel e.g. data_readers.cljc
@anmonteiro where is this file?
interesting stuff...
moving this q here: https://clojurians.slack.com/archives/clojurescript/p1476909015010076
@bhagany we can clarify int
but the other fns are really an orthogonal conversation entirely
for long
and unchecked-long
I think it’s easier - just removing the “Identical to `int’” part would resolve it
re: the others, @bhagany I agree, though we could be perhaps a bit more clear in those that they are there to ease portability not semantics
okay, I think I understand. Though, I do think that this particular behavior of int
is more likely to cause undetected bugs when porting than it is to ease it. It gets weird for larger numbers.
the pattern of N | 0
is used by JS engines thanks to asm.js/webasm as an optimization hint
so unless you have a brilliant idea how not damage hashing and the data structures there’s nothing to do
I don’t, and I’m not trying to argue that you should. I do think that the goal of easing portability isn’t well-served, but if there’s nothing to do, then there’s nothing to do.
the latter is unrealistic given the early performance goals - and now water under the bridge