Skip to content

Conversation

@EagleoutIce
Copy link
Member

No description provided.

Ellpeck and others added 30 commits November 19, 2024 16:41
@Ellpeck
Copy link
Member

Ellpeck commented Jan 8, 2025

Still left to do (carried over from #1160):

  • switch to npm package once available, to avoid wasm and (hopefully init)
    • Still allow the wasm backend (e.g., if we want to develop/explore part of it) with
      a user-supplied .wasm file.
  • Document the new backend and the way we can configure it (Flo, later)
    • Send info to Flo on what should be documented (especially self-building the wasm thingy for tree-sitter-r + how to specify it in the config / cli)
  • Also execute benchmarks with tree-sitter and r shell separately -> add as new matrix row
    • Also publish them on the website -> display above the current ones so that you have to scroll down to see the RShell ones
  • Fix the three-ish errors that occur with the tree sitter parser in the social-science benchmark suite (-> are these even still relevant? I don't remember tbh)
  • Allow setting the tree-sitter wasm path in the config also (currently only able to set the tree-sitter-r path)

@EagleoutIce EagleoutIce merged commit 687c7f4 into main Jan 16, 2025
17 checks passed
@EagleoutIce EagleoutIce deleted the new-parser-staging branch January 16, 2025 15:05
@EagleoutIce
Copy link
Member Author

This pull request is included in v2.2.0 (see Release v2.2.0 (Tree-Sitter Engine)).

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

Successfully merging this pull request may close these issues.

3 participants