You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently this requires file based actionless lexing in #21 I would really rather use rust-like raw string literals,
e.g. where r##"r#""#"## is the string "r#""#" than toml
To lex these we need a moded lexer which is currently difficult to dogfood, for dogfooding we'd either need some form of actionless moded lexer .l file format capable of this context sensitivity, or find a way to compile and execute actions or manually implemented lexers, e.g. by compiling them to wasm.
The alternate option here is to just use crimson, and either:
hack the grammar in a way which isn't correct and wouldn't allow nested quotes within strings, but would still be usable with nimbleparse_lsp.
just not be able to use crimson from nimbleparse_lsp because it depends on a lexer not representable with nimbleparse_lsp's limitations.
In the short term, the last option is most palatable. But you couldn't use the combination of crimson + nimbleparse_lsp until this is fixed.
The text was updated successfully, but these errors were encountered:
Currently this requires file based actionless lexing in #21 I would really rather use rust-like raw string literals,
e.g. where
r##"r#""#"##
is the string"r#""#"
than tomlTo lex these we need a moded lexer which is currently difficult to dogfood, for dogfooding we'd either need some form of actionless moded lexer
.l
file format capable of this context sensitivity, or find a way to compile and execute actions or manually implemented lexers, e.g. by compiling them to wasm.The alternate option here is to just use crimson, and either:
In the short term, the last option is most palatable. But you couldn't use the combination of crimson + nimbleparse_lsp until this is fixed.
The text was updated successfully, but these errors were encountered: