This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-17
Channels
- # adventofcode (96)
- # beginners (49)
- # boot (3)
- # cider (3)
- # cljs-dev (3)
- # clojure (112)
- # clojure-austin (2)
- # clojure-greece (35)
- # clojure-india (2)
- # clojure-sanfrancisco (1)
- # clojure-spec (1)
- # clojure-sweden (1)
- # clojurescript (27)
- # cursive (4)
- # data-science (1)
- # datomic (33)
- # defnpodcast (1)
- # duct (2)
- # editors (1)
- # emacs (4)
- # events (2)
- # figwheel (4)
- # fulcro (4)
- # hoplon (29)
- # instaparse (1)
- # jobs (1)
- # keechma (4)
- # lein-figwheel (2)
- # om (1)
- # parinfer (4)
- # perun (23)
- # reitit (11)
- # shadow-cljs (8)
- # specter (23)
- # uncomplicate (16)
Hi. Not sure if this is a shadow-cljs issue, but I was wondering whether you have experienced a problem with advanced compilation and regular expressions. It seems that the advanced optimizations is stripping out the backslashes from my regular expression patterns.
(println #"(\p{Lu}+[\p{Ll}\u0027\p{Ps}\p{Pe}]*)")
;; (while developing): #"(\p{Lu}+[\p{Ll}\u0027\p{Ps}\p{Pe}]*)"
;; (advanced compilation): #"(p{Lu}+[p{Ll}\u0027p{Ps}p{Pe}]*)"
Seems to just be for the "\p" regex tag
@mjmeintjes hmm that would be closure doing that. what is \p
, never used that before?
looks like that is es6, might work if you add :compiler-options {:language-out :ecmascript6}
Thanks, I'll try that. Also never used \p
before, but it is used in the funcool cuerdas string library, which currently does not work with advanced compilation due to this.