This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-03
Channels
- # announcements (2)
- # asami (1)
- # babashka (32)
- # beginners (125)
- # calva (4)
- # cider (1)
- # clj-kondo (16)
- # clj-together (1)
- # cljs-dev (15)
- # clojure (30)
- # clojure-australia (3)
- # clojure-europe (41)
- # clojure-italy (1)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-spec (68)
- # clojure-uk (28)
- # clojurescript (36)
- # conjure (2)
- # cryogen (1)
- # cursive (2)
- # data-science (2)
- # datascript (2)
- # datomic (70)
- # events (2)
- # fulcro (11)
- # graalvm (1)
- # jobs (4)
- # kaocha (4)
- # leiningen (4)
- # malli (52)
- # meander (21)
- # off-topic (11)
- # pathom (7)
- # pedestal (17)
- # reagent (23)
- # reitit (5)
- # remote-jobs (5)
- # reveal (7)
- # shadow-cljs (24)
- # spacemacs (36)
- # sql (21)
- # vim (18)
- # xtdb (7)
I’m playing around with the Google Closure JS parser, because I’m considering replacing the JS parser in Cursive with it. However doing some tests with it it seems like it doesn’t support ES6 decorators - does anyone know if that’s the case? I’d be surprised since AFAICT the idea is that it should be able to parse/handle anything, but I might be wrong about that.
aren't decorators still just a proposal? don't think they ever actually made it into es6?
otherwise the parser is updated fairly regularly with most features as long as they are on some standard level
Ah, ok. So presumably they’ll implement things like decorators if they become standard?
https://github.com/tc39/proposal-decorators looks like its still just a proposal