[elephant-ticket] #36: map-index :start and :end tag null handling

[elephant]

#36: map-index :start and :end tag null handling
-------------------------+--------------------------------------------------
 Reporter:  ieslick      |       Owner:  ieslick      
     Type:  defect       |      Status:  new          
 Priority:  minor        |   Milestone:  Release 0.7.0
Component:  system-wide  |     Version:               
 Keywords:  indexing     |  
-------------------------+--------------------------------------------------
 There is an inconsistency in the way that nil is handled by :start and
 :end.  Currently no keyword and a null valued keyword are treated the
 same, they mean the start and end of the list, respectively.  However this
 means that the nil value itself cannot be accessed by map-index.

 Can map-index operate over more than numbers, strings and oids?

-- 
Ticket URL: <http://trac.common-lisp.net/elephant/ticket/36>
elephant <http://common-lisp.net/project/elephant>
elephant