-
Current `@lexical/markdown` package supports shortcuts (auto-replace while typing), import and export relying on the same transformers configuration. It also uses RegExp parsing that does not have any…
-
SqlDatabaseContentRetriever.isSelect()
JSQLParser Not supported in Chinese, such as "select user_id as 用户ID from user"
**Please complete the following information:**
- LangChain4j version:0.31…
-
The object literal support introduced with #112 avoids changing some of the scope handling infrastructure and instead of modeling lexical scope as a single chain, it introduces direct access to scopes…
smarr updated
6 years ago
-
The [documentation](https://github.com/google/closure-templates/blob/master/documentation/concepts/templates.md#what-does-a-template-look-like
) for Closure Templates has examples of the param syntax…
-
I've added a comment on Gitter and decided that this is in fact bug:
R7RS spec say:
> The lexical syntax #n# serves as a reference to some object labelled by #n= the result is the same object as t…
-
Here is a very simple example to re-produce this issue:
```
/* description: Reproduce the issue. */
/* lexical grammar */
%lex
%{
yy.someArray3 = [];
yy.someValue2 = 'someValue';
%}
%%
"a"+…
-
## Description
Problem occuring with version 5.4.lucene900.1
We had a situation using SMUI, where product manager has input a phrase like "MacBook Pro 16" M3".
This has caused Solr to throw er…
-
The incremental GLR parsing algorithm doesn't take into account every possible alternative tokenization when looking for one that will result in a successful parse. Namely if two lexical rules can bot…
-
```bash
┌──(root💀8lgm-ShaftTruth)-[~/galaxy/src/frontend/parser]
└─# ./parser_test ../../../examples/a.glx
Lexical Analysis:
-----------------
Line 1, Column 1-5: IDENTIFIER "test"
Line 1, Colum…
-
I've seen some documents in the wild that have a `` comment block before the first `html` node (but after ``). I'm not super sure if that's "valid", but it is annoying that that's causing an error. Si…