Gregor Kappler

I investigated a bit and think the minor fix in pull request #316 suffices. `typeof(B)` in the example is now ``` JuliaDB.DNDSparse{NamedTuple{(:numid,),Tuple{Int64}},Int64} ```

`promote_type` seemed overkill at first to me; yet it might be required in corner cases.

This is experimentally released in 0.2.0 with limitations (no left recursion)

Glad you enjoy the package! It will be great to provide further parsers like JSONiq. You might be able to exclude otherwise valid matches with `Never()` or `NegativeLookbehind()` or `NegativeLookahead`?...

I checked your example, and the issue seems Julia 1.5.0 related. Your example works in Julia 1.4.1 on my side.

I worked around the compiler issue during sequence construction in order to support Julia 1.5 and be independent of the upstream fix - the performance dent will be negligible. Version...

I spent some time with it today and have added a few syntactic changes, so the EBNF parser syntax can be adapted very straightforwardly. I need to test a bit...

> > I wonder: You plobably do not just want to parse jsoniq but transform into a query object with some business logic, right? > Yes, sure. I am planning...

Hey, I updated CombinedParsers and wrote a [gist](https://gist.github.com/gkappler/11684795379d13ca6302d2374325e74c) for you with the scaffold. Note that I did not include parsers for NCName,D, _Char, etc. So it is not yet tested....

Thanks for the observation and pointer. It's also my observation that defining functions that construct parsers speeds up precompilation compared to defining parser variables. For a systematic optimization ChrisRackauckas note...