[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: seq-some-p and nil
|
From: |
John Mastro |
|
Subject: |
Re: seq-some-p and nil |
|
Date: |
Thu, 3 Sep 2015 10:35:19 -0700 |
Artur Malabarba <address@hidden> wrote:
> Agreed, and that's not the only case.
> Both `seq-some-p' and `seq-contains-p' are named as predicates but do
> not behave as predicates.
I think `seq-some-p' (or its successor) would also be more useful if it
promised to return the first matching element (the docstring says "any
element", though in practice it does return the first).
--
john
- seq-some-p and nil, Simen Heggestøyl, 2015/09/03
- Re: seq-some-p and nil, Stefan Monnier, 2015/09/03
- Re: seq-some-p and nil, Artur Malabarba, 2015/09/03
- Re: seq-some-p and nil, Nicolas Petton, 2015/09/03
- Re: seq-some-p and nil, Mark Oteiza, 2015/09/05
- Re: seq-some-p and nil, Nicolas Petton, 2015/09/06
- Re: seq-some-p and nil, Stefan Monnier, 2015/09/06
- Re: seq-some-p and nil, Nicolas Petton, 2015/09/07
- RE: seq-some-p and nil, Drew Adams, 2015/09/07
- Re: seq-some-p and nil, Stefan Monnier, 2015/09/07
- Re: seq-some-p and nil, Mark Oteiza, 2015/09/07