unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Harald Hanche-Olsen <hanche@math.ntnu.no>
To: monnier@iro.umontreal.ca
Cc: john.b.mastro@gmail.com, bozhidar.batsov@gmail.com, emacs-devel@gnu.org
Subject: Re: if-let and when-let: parallel or sequential
Date: Mon, 11 Aug 2014 18:40:24 +0200 (CEST)	[thread overview]
Message-ID: <20140811.184024.462063892661866315.hanche@math.ntnu.no> (raw)
In-Reply-To: <jwvr40nt7j1.fsf-monnier+emacs@gnu.org>

[Stefan Monnier <monnier@iro.umontreal.ca> (2014-08-11 14:42:19 UTC)]

> > if-let and when-let don’t make much sense with more than one binding
> > form.
> 
> Why do you think so?  If they only work for a single binding, the
> benefit is really minor.  It's only when you use several bindings that
> the benefit becomes more significant (the alternative being either
> a very deeply nested code, or separating the var's declarations from
> their initialization).

Indeed, it looks useful. But may I point out that the docstring seems
deficient? From the source code, I see that the the evaluation
short-circuits, so that evaluating

(defun foo () (insert "called foo\n") nil)
(defun bar () (insert "called bar\n") t)
(if-let ((FOO (foo))
	 (BAR (bar)))
    (insert "aye\n")
  (insert (format "nope: %s\n" BAR)))

produces

called foo
nope: nil

I can see how that is useful, but it needs to be documented better.
I'm afraid the resulting docstring may end up longer than the code,
but then so be it.

– Harald



  reply	other threads:[~2014-08-11 16:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10  2:44 if-let and when-let: parallel or sequential John Mastro
2014-08-10 15:22 ` Stefan Monnier
2014-08-11 12:01   ` Bozhidar Batsov
2014-08-11 14:42     ` Stefan Monnier
2014-08-11 16:40       ` Harald Hanche-Olsen [this message]
2014-08-11 17:49       ` Bozhidar Batsov
2014-08-11 20:55         ` Harald Hanche-Olsen
2014-08-12  2:43       ` Lars Magne Ingebrigtsen
2014-08-12  3:15       ` Richard Stallman
2014-08-12  3:30         ` John Mastro
2014-08-12 14:32           ` Elias Mårtenson

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=20140811.184024.462063892661866315.hanche@math.ntnu.no \
    --to=hanche@math.ntnu.no \
    --cc=bozhidar.batsov@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=john.b.mastro@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).