unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattiase@acm.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: master 6ebce84ff2b: Use t for non-nil default values in boolean defcustom declarations
Date: Sat, 29 Apr 2023 11:03:17 +0200	[thread overview]
Message-ID: <EA74A33D-1B8B-4AC8-9AC6-150F06FA45D1@acm.org> (raw)
In-Reply-To: <87ildfxhlt.fsf@gmx.de>

29 apr. 2023 kl. 09.39 skrev Michael Albinus <michael.albinus@gmx.de>:

> I'm just curious. Is there an advantage in using the (not (not ...))
> pattern? I would use (and ... t) instead, but perhaps your pattern is
> more performant? Or is it just a personal style?

I have no particular preference for either. If (and X t) is generally better liked, then it's fine to change to that.

Right now (not (not X)) is often but not always slightly shorter and faster but it doesn't matter in these cases and we could easily make both generate identical code.




  reply	other threads:[~2023-04-29  9:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <168268729579.28551.10245924430337302769@vcs2.savannah.gnu.org>
     [not found] ` <20230428130816.81449C22A07@vcs2.savannah.gnu.org>
2023-04-29  7:39   ` master 6ebce84ff2b: Use t for non-nil default values in boolean defcustom declarations Michael Albinus
2023-04-29  9:03     ` Mattias Engdegård [this message]
2023-04-29 11:07       ` Michael Albinus
2023-04-29 11:23     ` Andreas Schwab
2023-05-02  8:03       ` Robert Pluim
2023-05-02 16:42         ` Andreas Schwab

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=EA74A33D-1B8B-4AC8-9AC6-150F06FA45D1@acm.org \
    --to=mattiase@acm.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).