From: Yuan Fu <casouri@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: master c916f471caa 2/3: Add tree-sitter performance note
Date: Wed, 13 Sep 2023 21:08:37 -0700 [thread overview]
Message-ID: <5F1D1C9B-1CF3-4F77-BE30-605B23D89577@gmail.com> (raw)
In-Reply-To: <87bke54jiv.fsf@yahoo.com>
> On Sep 13, 2023, at 6:43 PM, Po Lu <luangruo@yahoo.com> wrote:
>
> Yuan Fu <casouri@gmail.com> writes:
>
>> branch: master
>> commit c916f471caada4eb9a4b7f9f53925a71525c694a
>> Author: Yuan Fu <casouri@gmail.com>
>> Commit: Yuan Fu <casouri@gmail.com>
>>
>> Add tree-sitter performance note
>> ---
>> admin/notes/tree-sitter/performance | 12 ++++++++++++
>> 1 file changed, 12 insertions(+)
>>
>> diff --git a/admin/notes/tree-sitter/performance b/admin/notes/tree-sitter/performance
>> new file mode 100644
>> index 00000000000..0e8351403af
>> --- /dev/null
>> +++ b/admin/notes/tree-sitter/performance
>> @@ -0,0 +1,12 @@
>> +TREE-SITTER PERFORMANCE NOTES -*- org -*-
>> +
>> +* Facts
>> +
>> +Incremental parsing of a few characters worth of edit usually takes
>> +less than 0.1ms. If it takes longer than that, something is wrong. There’s one time where I found tree-sitter-c takes ~30ms to incremental parse. Updating to the latest version of tree-sitter-c solves it, so I didn’t investigate further.
>
> Shouldn't this paragraph be filled to 72 columns, as you have done in
> the next one?
Indeed it should. Thanks for catching this. I use word-wrap so filled and unfilled paragraph look the same to me, apparently I forgot to fill this paragraph.
Yuan
next prev parent reply other threads:[~2023-09-14 4:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169465413983.20865.4955758569389021990@vcs2.savannah.gnu.org>
[not found] ` <20230914011540.707B4C04DAF@vcs2.savannah.gnu.org>
2023-09-14 1:43 ` master c916f471caa 2/3: Add tree-sitter performance note Po Lu
2023-09-14 4:08 ` Yuan Fu [this message]
2023-09-14 4:18 ` Po Lu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5F1D1C9B-1CF3-4F77-BE30-605B23D89577@gmail.com \
--to=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.