From: Eli Zaretskii <eliz@gnu.org>
To: casouri@gmail.com
Cc: 74612-done@debbugs.gnu.org
Subject: bug#74612: 30.0.90; [PATCH] Allow passing nil to treesit-node-match-p
Date: Thu, 05 Dec 2024 11:43:58 +0200 [thread overview]
Message-ID: <868qsuxy5d.fsf@gnu.org> (raw)
In-Reply-To: <86ed2r67vl.fsf@gnu.org> (message from Eli Zaretskii on Sun, 01 Dec 2024 11:59:58 +0200)
> Cc: 74612@debbugs.gnu.org
> Date: Sun, 01 Dec 2024 11:59:58 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: Yuan Fu <casouri@gmail.com>
> > Date: Sun, 1 Dec 2024 00:31:05 -0800
> > Cc: 74612@debbugs.gnu.org
> >
> >
> >
> > > On Nov 29, 2024, at 11:22 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > >
> > >> From: Yuan Fu <casouri@gmail.com>
> > >> Date: Fri, 29 Nov 2024 16:38:22 -0800
> > >>
> > >> Eli, are you ok with this patch on emacs-30? Almost all tree-sitter node functions allows user to pass nil for NODE, so treesit-node-match-p should too.
> > >
> > > Does this solve an actual problem you've seen somewhere (and if so,
> > > which problem), or does it solve a potential problem that didn't
> > > actually happen yet?
> >
> > I encountered this problem (more like an inconvenience, since without this feature I’d need to test for nullness before passing a node to treesit-node-match-p) when using treesit-node-match-p for some new code I’m writing for master branch. Since (treesit-node-match-p node “type name”) is easier to write and shorter than (equal (treesit-node-type node) “type name”) or (string-match-p “type name regex” (treesit-node-type node)), I’ve been using it liberally in new code :)
> >
> > >
> > > Also, does CHECK_TS_NODE allow nil or does it currently signal an
> > > error?
> >
> > CHECK_TS_NODE currently signals an error. All the tree-sitter node functions that accepts nil has the "if (NILP (node)) return Qnil” line before CHECK_TS_NODE (or treesit_check_node)
> >
> > If you’re not too comfortable with the change, we can apply it to master. It wouldn’t create any backward-incompatibility since this change makes treesit-node-match-p more lenient on its argument, not stricter. The drawback is treesit-node-match-p will be a bit more annoying to use.
>
> OK, please install on emacs-30, and thanks.
I see you did, so I'm closing this bug.
next prev parent reply other threads:[~2024-12-05 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 0:38 bug#74612: 30.0.90; [PATCH] Allow passing nil to treesit-node-match-p Yuan Fu
2024-11-30 7:22 ` Eli Zaretskii
2024-12-01 8:31 ` Yuan Fu
2024-12-01 9:59 ` Eli Zaretskii
2024-12-05 9:43 ` Eli Zaretskii [this message]
2024-12-06 7:24 ` Yuan Fu
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=868qsuxy5d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74612-done@debbugs.gnu.org \
--cc=casouri@gmail.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).