Fork me on GitHub
#shadow-cljs
<
2017-12-17
>
mjmeintjes00:12:56

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}]*)"

mjmeintjes00:12:41

Seems to just be for the "\p" regex tag

thheller09:12:39

@mjmeintjes hmm that would be closure doing that. what is \p, never used that before?

thheller09:12:14

looks like that is es6, might work if you add :compiler-options {:language-out :ecmascript6}

mjmeintjes20:12:35

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.

thheller22:12:35

nothing else happens? is it using CPU?

thheller22:12:09

maybe the logfile in target/shadow-cljs has some info?

hoppy22:12:26

it bails out after that