GNU bug report logs - #25129
26.0.50; seq-some function

Previous Next

Full log

Message #14 received at 25129 <at> debbugs.gnu.org (full text, mbox):

From: Nicolas Petton <nicolas <at> petton.fr>
To: Tino Calancha <tino.calancha <at> gmail.com>
Cc: 25129 <at> debbugs.gnu.org, Pierre Lorenzon <devel <at> pollock-nageoire.net>,
 tino.calancha <at> gmail.com
Subject: Re: bug#25129: 26.0.50; seq-some function
Date: Wed, 07 Dec 2016 11:24:58 +0100

[Message part 1 (text/plain, inline)]

Tino Calancha <tino.calancha <at> gmail.com> writes:

> Nicolas Petton <nicolas <at> petton.fr> writes:
>
>> Pierre Lorenzon <devel <at> pollock-nageoire.net> writes:
>>
>> Hi Pierre,
>>
>>> I well understand now that I must use seq-find instead of
>>> seq-some but I think that I will not be the only one being
>>> confused by these functions specifications !
>>
>> There is a mistake (extra if) in the documentation, I will fix that.
>>
>> Other than that, is the following less confusing?
>>
>>   Return non-nil if PRED returns non-nil for at least one element of SEQUENCE.
>>   If so, return the value returned by PRED.

> The previous doc string contains more information: it explicitely says
> that it returns the _first_ non-nil (PRED element).

Indeed, what about:

  Return non-nil if PRED returns non-nil for at least one element of SEQUENCE.
  If so, return the first non-nil value returned by PRED.

Cheers,
Nico

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.