Skip to content
This repository was archived by the owner on Jul 31, 2023. It is now read-only.
This repository was archived by the owner on Jul 31, 2023. It is now read-only.

Migrate tree-sitter and tree-sitter-ruby to WASM distribution #506

Closed

Description

@wingrunr21

Move tree-sitter and tree-sitter-ruby to use a WASM build instead of prebuilt binaries. This should yield a better user experience + allow us to drop prebuild.

More info here

Activity

  1. self-assigned this
    on Jul 11, 2019
  2. pinned this issue on Jul 15, 2019
  3. wingrunr21 commented on Jul 15, 2019

    @wingrunr21
    CollaboratorAuthor

    WASM support was started over the weekend. Just need to test a few things out and verify the solution works cross-platform. VSCode does not officially support WASM in extensions so want to make sure this is functioning as expected.

  4. razzeee commented on Jul 18, 2019

    @razzeee

    Btw just FYI, here's another VSCode addon that has been shipping wasm tree sitter files for some time now https://github.com/georgewfraser/vscode-tree-sitter/tree/master/parsers

  5. wingrunr21 commented on Jul 18, 2019

    @wingrunr21
    CollaboratorAuthor

    https://github.com/rubyide/vscode-ruby/tree/tree_sitter_wasm 😉

    The issue wasn't how to ship. The issue was support. I use the cursor to traverse the tree and a few features in that just landed yesterday.

  6. razzeee commented on Jul 18, 2019

    @razzeee

    VSCode does not officially support WASM in extensions so want to make sure this is functioning as expected.
    Just meant to mention that due to that, especially as I'm interested in your findings there. Might have implications for my LS implementation.

  7. minkir014 commented on Jul 18, 2019

    @minkir014

    When do you intend to fully convert prepuilt binaries to WASM to solve problems of prebuilt binaries instead of fixing node-tree-sitter problems since the PR against node-tree-sitter has some problems.

  8. wingrunr21 commented on Jul 18, 2019

    @wingrunr21
    CollaboratorAuthor

    @razzeee Ya, I think support works in practice but microsoft/vscode#65559. Luckily, the way tree-sitter is built the appropriate member functions for memory management can be defined in the types it ships vs those from the WASM spec or emscripten

    @minkir014 ASAP

  9. minkir014 commented on Jul 18, 2019

    @minkir014

    Have you encountered any problems with WASM or it's working properly??

  10. wingrunr21 commented on Aug 13, 2019

    @wingrunr21
    CollaboratorAuthor

    This change is in master. It will go out with the next release.

  11. added this to the v0.25.0 milestone on Aug 26, 2019
  12. minkir014 commented on Aug 27, 2019

    @minkir014

    When will WASM version of the extension go out??
    Maybe, this will help to fix all issues.

  13. wingrunr21 commented on Aug 27, 2019

    @wingrunr21
    CollaboratorAuthor

    I doubt it's going to fix all issues but I'm packaging a ton of bug fixes into the next release.

    I have one final issue to resolve and I will be doing the release. Fix is written just need to test an edge case I thought of today.

  14. wingrunr21 commented on Sep 2, 2019

    @wingrunr21
    CollaboratorAuthor

    This was shipped in v0.25.0. There was an issue with publishing that version to the Marketplace so v0.25.1 is the first version with the WASM switch.

  15. unpinned this issue on Sep 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementImproves upon existing functionality

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions