This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-07
Channels
- # announcements (11)
- # architecture (2)
- # babashka (84)
- # beginners (226)
- # calva (7)
- # chlorine-clover (4)
- # cider (29)
- # clara (17)
- # clj-kondo (23)
- # cljs-dev (58)
- # cljsrn (60)
- # clojure (172)
- # clojure-europe (24)
- # clojure-finland (2)
- # clojure-italy (6)
- # clojure-nl (8)
- # clojure-spec (4)
- # clojure-uk (22)
- # clojurescript (44)
- # conjure (39)
- # core-async (64)
- # cursive (76)
- # data-science (15)
- # duct (3)
- # emacs (2)
- # events (5)
- # fulcro (30)
- # helix (4)
- # jackdaw (5)
- # juxt (1)
- # kaocha (1)
- # leiningen (4)
- # off-topic (9)
- # pathom (22)
- # re-frame (9)
- # reagent (33)
- # reitit (3)
- # ring (10)
- # ring-swagger (2)
- # shadow-cljs (192)
- # spacemacs (27)
- # specter (2)
- # sql (59)
- # vim (2)
Will do
So repeatable but not new since it fails on 1.10.597 and 1.10.758. I can get it to consistently fail with :whitespace and :simple optimisations. Dev repl and compile, and :advanced optimisations is fine.
I'll raise an issue
Yep seems the same. Hmm, perhaps I should close as a DUP.
Perhaps things have evolved a little since then :advanced seems to work. (Or my example was too simple - I’ll check this... still works with more complex example under :advanced)
Thanks for the link.
np, I vaguely remembered seeing java.nio.file.InvalidPathException: Illegal char <:>
before somewhere 😛 but can't remember what I did in shadow-cljs to fix it
Yeah, I see your comments there. Do you still have the workaround in place?
I think somewhere paths must be normalized so it doesn't write windows paths into JS output
yeah my hack is still around but was fixing a different issue with [synthetic:1]
sources (which the closure compiler sometimes adds itself)
Bug?
(into (transient []) [1 2 3]) ;; Error: No protocol method ICollection.-conj defined for type cljs.core/TransientVector: [object Object]
(implements? IEditableCollection (transient [])) ;; false
there's a similar ticket in clj I think
actually, I am misconnecting, although there are some old issue with the hierarchy for transient colls
I'm not sure how closely cljs matches clj in this area
@roman01la not a bug that doesn't work in Clojure either
@olivergeorge thanks
feel free to chime in on other old ugly bugs that you believe should be fixed up for the next release
@dnolen Interesting, but PersistentVector
does implement IEditableCollection
, how's that (implements? IEditableCollection (transient []))
results in false
?
(transient []) is not a PersistentVector
ah right, thanks!
@alexmiller website could use a bump
yeah I'm most curious about how they are going to do the namespacing system. I'd expect them to move to regular import/export
for the TS sources. not sure if they are going to bother to keep the old namespaces in place since closure can consume import/export just fine
oh that’s literally what the message is about: don’t require GCC users to have to compile TS 🙃
which is a bit of a bummer; I found myself wanting to write some JS for some lib code, and decided to try out TS. I started thinking about how I would include it in a CLJS lib/app. Atm I guess the best option is to ship the compiled artifacts to NPM
Maybe I could compile the TS code to closure JS and then ship that in my jar with CLJS code
@alexmiller hrm the ClojureScript website seems broken?
yeah, I'm working on it
don't experiment with stuff in prod
should be fixed