-
### Description
SwiftParser currently can’t handle DocC-style abridged signatures such as:
```
init(String.Index, x:(Int) -> Int) rethrows
```
as they are considered malformed parse trees.
…
-
For instance:
```
(1[&type="X"]:0.032081690609203524,2[&type="X"]:0.032081690609203524)[&type="X"]:0.0;
```
is incorrectly parsed as `(1:1,2:1);`. Additional annotations can produce errors. Do you…
-
Since lark version 1.2.1, there seem to be (more?) ambiguities produced for our syntax.
While the syntax is ambiguous, we used prioritiies to fix this before.
```
%import common.INT
%import comm…
-
When analyzer fails, seeing the intermediate parse trees generated is useful.
1 - parse trees stop being generated before the error.
2 - parse trees can help debug the problem, as error often occurr…
-
This is a long-term idea: I'm starting to wonder if we should have an enhanced version of trees that might incorporate additional info such as
- ~punctuation~ (added in regular trees)
- ~lemmas wh…
-
While trying to parse a specific sentence from the Treebank corpus these two parsers behave strangely.
This is the sentence from treebank:
`['A', 'form', 'of', 'asbestos', 'once', 'used', '*', '*', …
-
What do you think about the generating trees by parsing yaml file.
something like
```
root:
name: Reality
type: composites.Parallel
children: child_a
child_a:
name: My Timer
typ…
-
Good morning sir :)
I would like to share my notes (still in progress) on Bunda-Gerth parsing that was mentioned few times in APL Farm chatroom. I cannot promise time frame I can commit to but you …
-
the current components work great for retrieving single values from named properties in a JSON string, but often you will be storing arrays of values in a named property.
The current output creates…
-
Having various operator token kinds is relevant during parsing, but they should potentially all be remapped to `K"Identifier"` afterward because their special status as operators is no longer meaningf…