[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: seq-some-p and nil
|
From: |
Artur Malabarba |
|
Subject: |
Re: seq-some-p and nil |
|
Date: |
Thu, 3 Sep 2015 18:19:46 +0100 |
2015-09-03 17:42 GMT+01:00 Stefan Monnier <address@hidden>:
>> Two solutions come to my mind: 1) Make `seq-some-p' a pure t/nil
>> predicate, or 2) Make it behave like `some' in Common Lisp, which is
>> to return the first non-nil value which is returned by an invocation
>> of the predicate. So in CL:
>
> I think that functions named "<foo>-p" should return values which are
> fundamentally booleans
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.
- 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 <=
- 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