This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-15
Channels
- # adventofcode (121)
- # bangalore-clj (5)
- # beginners (46)
- # boot-dev (9)
- # cider (20)
- # cljs-dev (7)
- # cljsrn (1)
- # clojure (341)
- # clojure-austin (7)
- # clojure-greece (144)
- # clojure-india (3)
- # clojure-italy (5)
- # clojure-spain (1)
- # clojure-spec (34)
- # clojure-sweden (3)
- # clojure-uk (90)
- # clojurescript (24)
- # core-async (1)
- # core-logic (7)
- # cursive (108)
- # datascript (2)
- # datomic (39)
- # events (1)
- # fulcro (225)
- # graphql (8)
- # hoplon (86)
- # instaparse (12)
- # jobs-discuss (2)
- # jvm (4)
- # keechma (1)
- # lein-figwheel (2)
- # leiningen (12)
- # off-topic (26)
- # onyx (35)
- # other-languages (1)
- # pedestal (3)
- # planck (11)
- # re-frame (12)
- # reagent (12)
- # reitit (5)
- # spacemacs (48)
- # specter (29)
- # sql (2)
- # test-check (1)
- # unrepl (71)
is there some way in instaparse to ask for all possible grammar elements at certain point of the parse tree?
meaning, I have parse result, I take a specific point in that parse tree and the would get a list of parse elements that could go there
I could theoretically write an EBNF analyzer to do just this but don’t feel like it unless I have to
since I think instaparse already does this somewhere under the hood and has the necessary information
hmm, there is instaparse.cfg/ebnf
, need look at it and if it would provide the necessary information
@niklas.collin not sure what you're asking. what would be an example of using this functionality?
There have been a few discussions about generating data for a parser, or listing possible inputs to a parser
Not sure the best path to exposing that
are you sure ebnf
is what you want? That just creates a combinator based on an EBNF spec, it doesn't generate a list of things that could go there