From: Stephen Leake <stephen_leake@stephe-leake.org>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: emacs-devel@gnu.org
Subject: Re: [SPAM UNSURE] Re: [SPAM UNSURE] Maybe we're taking a wrong approach towards tree-sitter
Date: Fri, 30 Jul 2021 11:44:28 -0700 [thread overview]
Message-ID: <86y29nmyk3.fsf@stephe-leake.org> (raw)
In-Reply-To: <262fdcc2-16ea-0548-a854-15f012c9dac1@piermont.com> (Perry E. Metzger's message of "Thu, 29 Jul 2021 20:19:15 -0400")
"Perry E. Metzger" <perry@piermont.com> writes:
> On 7/29/21 19:28, Stephen Leake wrote:
>> "Perry E. Metzger" <perry@piermont.com> writes:
>>
>>> That's not true. Tree Sitter is not written even partially in Rust. It
>>> does have Rust bindings for people who use Rust.
>> https://github.com/tree-sitter/tree-sitter/tree/master/cli/src
>>
> That's an optional CLI and is not part of the library runtime.
Yes, and the optional CLI is part of the tree-sitter project, so the
statement "Tree Sitter is not written even partially in Rust" is simply
wrong.
Please be more careful when you say "tree-sitter", but mean
"tree-sitter runtime"; it is not always clear from context.
--
-- Stephe
next prev parent reply other threads:[~2021-07-30 18:44 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 1:57 Maybe we're taking a wrong approach towards tree-sitter Andrei Kuznetsov
2021-07-28 3:53 ` [SPAM UNSURE] " Stephen Leake
2021-07-28 8:23 ` Manuel Giraud
2021-07-28 11:48 ` Andrei Kuznetsov
2021-07-28 13:04 ` Eli Zaretskii
2021-07-28 13:14 ` Andrei Kuznetsov
2021-07-28 13:27 ` Eli Zaretskii
2021-07-28 13:31 ` Andrei Kuznetsov
2021-07-28 14:24 ` Dmitry Gutov
2021-07-28 14:36 ` Dmitry Gutov
2021-07-28 14:51 ` Daniele Nicolodi
2021-07-28 16:10 ` Eli Zaretskii
2021-07-28 16:24 ` Perry E. Metzger
2021-07-28 16:29 ` Eli Zaretskii
2021-07-29 23:12 ` Stephen Leake
2021-07-29 23:21 ` Yuan Fu
2021-07-30 18:38 ` Stephen Leake
2021-07-30 0:41 ` Andrei Kuznetsov
2021-07-30 12:06 ` Arthur Miller
2021-07-30 12:52 ` Óscar Fuentes
2021-07-30 13:30 ` Arthur Miller
2021-07-30 13:57 ` Ergus
2021-07-30 14:52 ` Arthur Miller
2021-07-30 13:59 ` Eli Zaretskii
2021-07-30 15:45 ` Arthur Miller
2021-07-30 13:32 ` Ergus
2021-07-30 15:07 ` Arthur Miller
2021-08-02 22:13 ` Perry E. Metzger
2021-07-30 18:42 ` Stephen Leake
2021-07-30 6:05 ` Eli Zaretskii
2021-07-31 12:12 ` Stephen Leake
2021-07-31 13:07 ` Eli Zaretskii
2021-07-31 16:55 ` Stephen Leake
2021-07-31 17:12 ` Eli Zaretskii
2021-07-28 11:43 ` Andrei Kuznetsov
2021-07-28 11:50 ` Eli Zaretskii
2021-07-28 12:06 ` Andrei Kuznetsov
2021-07-28 13:05 ` Eli Zaretskii
2021-07-28 13:16 ` Andrei Kuznetsov
2021-07-28 12:36 ` Ergus
2021-07-28 13:07 ` Andrei Kuznetsov
2021-07-28 13:16 ` Eli Zaretskii
2021-07-28 13:27 ` Andrei Kuznetsov
2021-07-28 13:32 ` Eli Zaretskii
2021-07-28 13:38 ` Andrei Kuznetsov
2021-07-28 14:41 ` Manuel Giraud
2021-07-28 15:15 ` Perry E. Metzger
2021-07-28 16:10 ` Eli Zaretskii
2021-07-29 23:25 ` [SPAM UNSURE] " Stephen Leake
2021-07-30 0:54 ` Andrei Kuznetsov
2021-07-30 3:02 ` Andrei Kuznetsov
2021-07-30 18:48 ` Stephen Leake
2021-07-28 15:12 ` Perry E. Metzger
2021-07-29 23:28 ` Stephen Leake
2021-07-30 0:19 ` Perry E. Metzger
2021-07-30 18:44 ` Stephen Leake [this message]
2021-07-29 4:35 ` Richard Stallman
2021-07-28 15:09 ` Perry E. Metzger
2021-07-29 23:35 ` Stephen Leake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86y29nmyk3.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).