Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

consider wasm based lexers #23

Open
ratmice opened this issue Jun 4, 2022 · 0 comments
Open

consider wasm based lexers #23

ratmice opened this issue Jun 4, 2022 · 0 comments

Comments

@ratmice
Copy link
Owner

ratmice commented Jun 4, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant