[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: seq-some-p and nil
From: |
Stefan Monnier |
Subject: |
Re: seq-some-p and nil |
Date: |
Thu, 03 Sep 2015 12:42:46 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
> 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, but whose non-nil value is unspecified (they
can return any non-nil value they fancy and the callers should make
assumptions about that non-nil return value).
Other than that, the CL behavior looks sane to me.
Stefan
- seq-some-p and nil, Simen Heggestøyl, 2015/09/03
- Re: seq-some-p and nil,
Stefan Monnier <=
- 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