This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-27
Channels
- # announcements (10)
- # aws (11)
- # beginners (158)
- # calva (8)
- # cider (14)
- # clj-kondo (1)
- # cljsrn (1)
- # clojure (83)
- # clojure-europe (5)
- # clojure-italy (25)
- # clojure-nl (3)
- # clojure-spec (12)
- # clojure-uk (20)
- # clojurescript (72)
- # community-development (18)
- # core-async (4)
- # core-logic (19)
- # cursive (11)
- # datomic (21)
- # duct (6)
- # events (1)
- # figwheel-main (3)
- # fulcro (15)
- # ghostwheel (1)
- # jobs (1)
- # leiningen (16)
- # off-topic (45)
- # onyx (3)
- # pathom (7)
- # perun (1)
- # ring (3)
- # shadow-cljs (48)
- # spacemacs (10)
- # specter (1)
- # sql (24)
- # tools-deps (7)
- # vscode (7)
- # xtdb (14)
@pez while rabbit-holing on this, i noticed that vscode-tree-sitter uses web-tree-sitter (https://github.com/tree-sitter/tree-sitter/tree/master/lib/binding_web). i'm not confident about this, but it appears that by using web-tree-sitter, vscode-tree-sitter avoids compiling tree sitter c bits for each platform -- instead it uses wasm. do you know if vscode extensions can work with wasm? i came across: https://github.com/microsoft/vscode/issues/65559#issuecomment-471279633 and wondered what the status was.
thanks -- i had assumed using tree sitter would lead to having to compile 3 different binaries for inclusion in an extension or have 3 different extensions. on a related note, i didn't know that this was under consideration: https://github.com/microsoft/vscode/issues/23251 the "when" seems very vague.