[Neo tickets] #204: PrefetchingIterator uses null to signal that there are no more elements

neo4j.org noreply at neo4j.org
Wed Nov 11 09:10:27 CET 2009


#204: PrefetchingIterator uses null to signal that there are no more elements
-----------------------------------------+----------------------------------
 Reporter:  daniel.kristensen at gmail.org  |        Owner:  mattias 
     Type:  bug report                   |       Status:  assigned
 Priority:  major                        |    Milestone:          
Component:  neo-utils                    |   Resolution:          
 Keywords:                               |  
-----------------------------------------+----------------------------------
Changes (by mattias):

 * cc: daniel.kristensen at gmail.org (added)
  * status:  new => assigned


Comment:

 Hi daniel.

 To your first point about the !PrefetchingIterator using null: You
 definately got a point there, however I haven't come across a scenario of
 such iteration, but it's definately possible. Although it may be a corner
 case and we could implement another such iterator which does that.

 Your second point I agree with, it felt bad to implement it like that and
 it'd probably be better with a method as you propose. I'll look into that!

-- 
Ticket URL: <https://trac.neo4j.org/ticket/204#comment:2>
neo4j.org <http://trac.neo4j.org/>
The Neo4J.org Issue Tracker


More information about the Tickets mailing list