On Wed, Dec 21, 2011 at 12:11 AM, Jean-Pierre Bergamin
wrote:
> I created an issue for that: https://github.com/neo4j/community/issues/141
I was bitten by IndexHits implementing Iterable myself yesterday, and
also agree that it's bad.
But it's not the only one. A quick search through community s
I created an issue for that: https://github.com/neo4j/community/issues/141
Best regards,
James
___
NOTICE: THIS MAILING LIST IS BEING SWITCHED TO GOOGLE GROUPS, please register
and consider posting at https://groups.google.com/forum/#!forum/neo4j
Neo4j
That indeed is evil, JP.
Could you raise an issue on this please? Please copy even your
explanation in there. Fully agree.
Cheers,
/peter neubauer
TC CEO of the year - vote for Emil Eifrém!
http://crunchies2011.techcrunch.com/nominate/
Google:neubauer.peter
Skype:peter.neubauer
Phone: +46 704
Dear neo4j community and developers
For the second time we stumbled about Iterables that are no Iterables
in Neo4j. IndexHits e.g. extends Iterator and Iterable and states in
its documentation that is not really an iterable but always returns
"this" in calls to iterator(). So far so good.
Now whe
4 matches
Mail list logo