This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-12
Channels
- # aleph (3)
- # announcements (7)
- # babashka (22)
- # beginners (44)
- # calva (19)
- # chlorine-clover (1)
- # cider (20)
- # clj-kondo (55)
- # clojure (100)
- # clojure-austin (9)
- # clojure-europe (19)
- # clojure-italy (19)
- # clojure-nl (13)
- # clojure-portugal (2)
- # clojure-uk (7)
- # clojurescript (38)
- # community-development (3)
- # conjure (2)
- # cryogen (57)
- # cursive (6)
- # datalog (3)
- # datomic (24)
- # emacs (17)
- # exercism (8)
- # fulcro (3)
- # holy-lambda (8)
- # jobs (6)
- # jobs-discuss (9)
- # joker (3)
- # lambdaisland (5)
- # leiningen (5)
- # music (9)
- # nextjournal (1)
- # nrepl (2)
- # off-topic (9)
- # other-languages (4)
- # pathom (6)
- # polylith (23)
- # re-frame (5)
- # reagent (5)
- # remote-jobs (1)
- # reveal (1)
- # shadow-cljs (3)
- # tools-build (1)
- # tools-deps (3)
- # xtdb (2)
We released a major new update to Regal, including supporting for Google's RE2 and lazy-qualifiers (like +`?` and *?
) Thank you to @dandorman and @zoharkfor the contributions! https://github.com/lambdaisland/regal/releases/tag/v0.0.143
I didn't do any performance testing as a part of merging the PR. @zohark might know, although I'm not sure performance was a motivation for using RE2 in his project.
My use case was building expressions for both Java and Google Bigquery, and not performance.
But about performance, Java's RE engine has trouble when there are a lot of alternations (aaaaa|aaaab|aaaac)
etc. because of backtracking, whereas re2 works in linear time. But re2 doesn't support lookahead/behind and such as a consequence. I actually ran into that alternation issue in my project, so having an easy way to switch to re2 there really helped!