This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-29
Channels
- # adventofcode (4)
- # beginners (113)
- # boot (165)
- # cider (192)
- # cljsrn (82)
- # clojure (148)
- # clojure-austin (6)
- # clojure-russia (22)
- # clojure-spec (45)
- # clojure-uk (19)
- # clojurescript (153)
- # core-async (5)
- # cursive (7)
- # datomic (2)
- # defnpodcast (2)
- # emacs (1)
- # hoplon (617)
- # instaparse (10)
- # lein-figwheel (19)
- # luminus (2)
- # off-topic (12)
- # om (3)
- # onyx (36)
- # pedestal (1)
- # protorepl (43)
- # re-frame (8)
- # ring (7)
- # specter (17)
- # testing (2)
- # untangled (117)
- # yada (12)
I don't imagine there's a way to unparse something
@gfredericks What are you trying to accomplish by "unparsing", and how much control do you have over the parsing?
@gfredericks: some discussion has happened about this in https://github.com/Engelberg/instaparse/issues/82
which I just noticed you saw and commented on
The fact that "hide tag" (`<>`) is a thing makes it a complex problem to provide unparsing as a general solution
also lookahead / negative lookahead
I want a canonical printer. Potentially pretty printing...which sounds hard
So no, not reconstructing the original input exactly