From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: Tree-sitter introduction documentation Date: Thu, 29 Dec 2022 17:12:35 +0000 Message-ID: <87358ygmm4.fsf@posteo.net> References: <868rj6vfep.fsf@gmail.com> <4895891b-e5ea-9c37-f51b-df2e479ee758@yandex.ru> <83y1qt11xq.fsf@gnu.org> <9eb013da-d0fc-8e17-c6e3-1e8f913aebfa@yandex.ru> <83pmc50xxc.fsf@gnu.org> <71cfe4e8-3bb8-b0a6-9be5-8c0a6d92cfab@yandex.ru> <83h6xg29z3.fsf@gnu.org> <838ris22n4.fsf@gnu.org> <8335901zz3.fsf@gnu.org> <87cz84y5le.fsf@posteo.net> <3F91FDEA-881A-49DB-BB52-5A0D81C004CE@gmail.com> <87k02aihrz.fsf@posteo.net> <86ce08480352653995b8@heytings.org> <87r0wigqnb.fsf@posteo.net> <86ce08480372e6e5db04@heytings.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12622"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Yuan Fu , Stefan Monnier , Eli Zaretskii , Dmitry Gutov , Tim Cross , emacs-devel@gnu.org To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 29 18:20:52 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pAwaI-00031T-SE for ged-emacs-devel@m.gmane-mx.org; Thu, 29 Dec 2022 18:20:50 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pAwSJ-00063H-O8; Thu, 29 Dec 2022 12:12:35 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pAwSH-00062w-Vg for emacs-devel@gnu.org; Thu, 29 Dec 2022 12:12:34 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pAwSF-0007CK-Iv for emacs-devel@gnu.org; Thu, 29 Dec 2022 12:12:33 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 26C2A2401FD for ; Thu, 29 Dec 2022 18:12:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1672333950; bh=8vBVdo71tSDHPgYQbw5RjaNV8HTYEnjyJYHwLtzf3Ss=; h=From:To:Cc:Subject:Date:From; b=Rb8WO6ROKOl+U8fVM3iVOau2dJCFBu/QsS0frpCTBkAXW4SQuOqZIaxgep6laXbZf YyAlRc52Qll8SZYGIR4UqQV8a+orGRGdYeuGk6b2rNCuxeooTTOInm0Sug6jBAC+YE xIlZA1VBNvq3bl4ISr+i8nOKgfY8osdBDPyqnVbNBFzyKpxqAVxplRpSVpKVG9BuBJ f+PICN5NSFRAGmeGX5XJjURECNuYgYcxzJqjZEi5AXNgHoanYbiY5b5Z4bi2yy9q/V nmp4/rX8x3rfdrslvJzIcktDOjdRvp7BQv9NFK+qSz74FvAO5/rLvodYcr3PhO/D2v z1xLmkuaDVp+A== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NjZhD6xC0z9rxL; Thu, 29 Dec 2022 18:12:28 +0100 (CET) In-Reply-To: <86ce08480372e6e5db04@heytings.org> (Gregory Heytings's message of "Thu, 29 Dec 2022 17:00:52 +0000") Received-SPF: pass client-ip=185.67.36.66; envelope-from=philipk@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:302050 Archived-At: Gregory Heytings writes: >>> That's not possible, no, at least not without a lot of >>> complications that do not seem worth the price, compared to >>> installing Node.js. And note that even if that were feasible, it >>> would only solve the first half of the problem: to transform a >>> grammar.js file into its corresponding parser.c file, you also need >>> the tree-sitter command line program. >> >> Not necessarily, that could also be ported to JavaScript. >> > > I'm puzzled. What would be the benefit of doing that? Installing > Node.js and tree-sitter is easy. Not always, I always have issues with Node.js on Debian Stable. Especially when external dependencies are added to the mix. The advantage would be a simpler toolchain that would require less effort for the user to get running, instead of dealing with version mismatches and dependency resolution. >> >> That being said, I don't imagine it to be an easy process. >> > > Indeed. The generator is about 13500 lines of non-trivial Rust code. I was under the impression that the main part of generating C code was bundled in here: https://github.com/tree-sitter/tree-sitter/blob/master/cli/src/generate/render.rs But I see that it appears to include some other modules, which is probably where a lot of the logic happens :/ >>> Indeed, grammar authors are not limited to the standard Node.js >>> API, they can import other libraries. >> >> How common is this in practice? Is it encouraged? > > I don't know. I'd guess it is not frequent, but neither encouraged > nor discouraged. This would be a nice thing to clarify. I have also found out that there is a Javascript interpreter written in Rust that could be used to remove the Node.js dependency: https://github.com/boa-dev/boa. It would be interesting to suggest this upstream and see if something like this could be used at some point.