This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-03
Channels
- # aleph (7)
- # announcements (6)
- # babashka (34)
- # beginners (5)
- # calva (1)
- # cider (3)
- # clerk (11)
- # clj-http (1)
- # clj-kondo (35)
- # clojars (6)
- # clojure (114)
- # clojure-australia (1)
- # clojure-brasil (2)
- # clojure-europe (73)
- # clojure-hamburg (3)
- # clojure-nl (1)
- # clojure-norway (27)
- # clojure-uk (4)
- # events (3)
- # graalvm (13)
- # gratitude (4)
- # helix (17)
- # hoplon (1)
- # hyperfiddle (65)
- # instaparse (4)
- # jobs-discuss (6)
- # lsp (2)
- # meander (2)
- # rdf (4)
- # re-frame (51)
- # reitit (28)
- # releases (1)
- # sci (20)
- # shadow-cljs (9)
- # tools-deps (4)
- # xtdb (44)
Thanks @aengelberg and @ghaskins, actually my insta/parse
was working as expected (prioritizing the correct version) but insta/parses
is still showing more than one possibility, though I guess that this might prevent cases where the first parse is not the one I want right?
Ah, yes, ordered choice still gives you all the possible parses. If you want it to be unambiguous, try a negative look ahead.
op-degrade = (<'?'> degrade-amount) | <'?'> !degrade-amount
Thanks, that works great!
I believe I was missusing the negative look ahead syntax. I appreciate the example!