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

Question: JS and WASM JS target support #9

Open
lppedd opened this issue Jul 5, 2024 · 4 comments
Open

Question: JS and WASM JS target support #9

lppedd opened this issue Jul 5, 2024 · 4 comments
Labels
question Further information is requested

Comments

@lppedd
Copy link

lppedd commented Jul 5, 2024

On the linked website I can read

JS and WASM JS will not be supported.

What's the reason behind this choice?

@ObserverOfTime ObserverOfTime added the question Further information is requested label Jul 5, 2024
@ObserverOfTime
Copy link
Member

It's not possible to use the C API directly in JS (as far as I know).
The only option would be to delegate to tree-sitter/web-tree-sitter.

@lppedd
Copy link
Author

lppedd commented Jul 5, 2024

Wrapping and delegating to node-tree-sitter seems like a reasonable idea.
That would make kotlin-tree-sitter a valid alternative to antlr-kotlin.

Supporting a JS target would be cool. WebAssembly can wait, it's still not widespread.

@ObserverOfTime
Copy link
Member

Do you have a use case for it?

@lppedd
Copy link
Author

lppedd commented Jul 6, 2024

We might want to experiment with tree-sitter for parsing stuff on a VS Code extension, using Kotlin code compiled to JS.

But the general picture for me is the expansion of the KMP and K/JS library ecosystem.

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

No branches or pull requests

2 participants