-
When executing a comment-only bql such as,
```
-- hoge
```
we get a parsing error.
```
Cannot set up the server context: failed to parse string as BQL statement
statement has a syntax error near li…
-
Hello,
I have been using Arpeggio as a tool to test a grammar (re)written in PEG recently. It's a really good tool (a bit hard to understand the debugging output sometimes), but I found out that it…
-
Hi, where i can find any documentation for parser generator?
-
I hope you don't mind that I ask another about grammar but I'm stuck and the error makes no sense to me.
Example to reproduce
````python
from parsimonious.grammar import Grammar
grammar = Gram…
-
I'm really new to PEGs so I'm sure I'm writing some totally messed up grammars. When the parse succeeds, I'm able to tweak things because there's a very helpful dump that shows me exactly the process …
-
(First of all I don't even know if this is theoretically possible.)
Idea is to have `GLRParser.parse(...)` return iterator, and each value in that iterator is computed on demand. Parses are sorted …
-
### Issue type
* [x] Bug Report
### Prerequisites
Non-urgent but annoying.
### Description
A false return value from a predicate is reported as a failure to match the next pattern in th…
-
Pegged uses `#` as the start of its line comment which does not work well with D's `q{}` strings. This is not an issue of taste, the D compiler rejects `#` as a token. Literally anything else would be…
-
Hi! I would like to claim bounty #4.
Here is my work: https://github.com/grepsuzette/joeson
port of joeson (from coffeescript/js to golang)
as literal as possible
Verbatim of the bounty (https…
-
this is cool, thanks for starting down this path with PyTorch. I came here from the HN discussion. I have been focusing on llama 2 since it seems for me to be a bit of a tipping point and its time to …