all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Xiyue Deng <manphiz@gmail.com>
Cc: "67669@debbugs.gnu.org" <67669@debbugs.gnu.org>
Subject: bug#67669: 29.1; Drop text suggesting using `and' to replace `if'
Date: Fri, 8 Dec 2023 15:37:01 +0000	[thread overview]
Message-ID: <SJ0PR10MB54884559A8A3E55A2994A8E4F38AA@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83o7f11a9f.fsf@gnu.org>

> (let (baz)
>   (setq foo (concat "bar" (if (stringp baz) baz))))
>   => "bar"
> 
> Here 'if' returns nil, and we use the feature of
> 'concat' to ignore nil arguments.

IMO the meaning/behavior is clearer with `and':

 (let (baz)
   (setq foo (concat "bar" (and (stringp baz) baz))))

But again, such stylistic concerns are exactly that.





  parent reply	other threads:[~2023-12-08 15:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 21:47 bug#67669: 29.1; Drop text suggesting using `and' to replace `if' Xiyue Deng
     [not found] ` <handler.67669.B.170189926211616.ack@debbugs.gnu.org>
2023-12-06 22:08   ` Xiyue Deng
2023-12-07  6:28 ` Eli Zaretskii
2023-12-07  9:08   ` Xiyue Deng
2023-12-07 10:16     ` Eli Zaretskii
2023-12-07 17:49       ` Xiyue Deng
2023-12-07 17:56         ` Eli Zaretskii
2023-12-07 19:54           ` Xiyue Deng
2023-12-07 20:22             ` Eli Zaretskii
2023-12-07 20:37               ` Xiyue Deng
2023-12-07 21:29                 ` Drew Adams
2023-12-08  9:11                   ` Xiyue Deng
2023-12-08  6:25                 ` Eli Zaretskii
2023-12-08  9:07                   ` Xiyue Deng
2023-12-08 15:37                   ` Drew Adams [this message]
2023-12-07 19:37         ` Drew Adams
2023-12-07 20:00           ` Xiyue Deng
2023-12-08 10:45         ` Sean Whitton
2023-12-08 22:41           ` Xiyue Deng

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=SJ0PR10MB54884559A8A3E55A2994A8E4F38AA@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=67669@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=manphiz@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 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.