[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] [Chicken-bugs] #352: Review of andmap & ormap procedu
From: |
Chicken Scheme |
Subject: |
[Chicken-janitors] [Chicken-bugs] #352: Review of andmap & ormap procedures in Unit Library |
Date: |
Fri, 09 Nov 2007 10:31:59 -0000 |
#352: Review of andmap & ormap procedures in Unit Library
-----------------------------------------------+----------------------------
Reporter: Jon Strait <address@hidden> | Type: defect
Status: new | Priority: minor
Component: core libraries | Version: 2.7
Keywords: |
-----------------------------------------------+----------------------------
andmap currently returns #t if all invocations of its map procedure return
a true value. This is similar to the every procedure in SRFI-1, but not
quite as useful, because at least the every procedure returns the final
value on success. andmap could be made most useful by returning the list
of the results after map, which is, of course, the same as #t. I think
that this is what the name 'andmap' would imply. I'm thinking of and-let*
and how it would generate a useful result the same as let* does.
ormap seems to be identical to the 'any' procedure in SRFI-1.
--
Ticket URL: <http://trac.callcc.org/ticket/352>
Chicken Scheme <http://www.call-with-current-continuation.org/>
The CHICKEN Scheme-to-C compiler
- [Chicken-janitors] [Chicken-bugs] #352: Review of andmap & ormap procedures in Unit Library,
Chicken Scheme <=