commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <gudnabr...@gmail.com>
Subject Re: General API question: returning Iterator, Iterable or even Collection?
Date Mon, 03 Jun 2013 14:45:11 GMT
On Mon, Jun 3, 2013 at 9:15 AM, Jörg Schaible
<Joerg.Schaible@scalaris.com>wrote:

> Emmanuel Bourg wrote:
>
> > Le 03/06/2013 13:44, Stefan Bodewig a écrit :
> >
> >> My personal preference would be Iterable as well as the consumer may
> >> iterate over the return value multiple times without copying stuff
> >> around, but I may be missing something.
> >
> > I like Iterable for the ease of use in a foreach loop. But there is a
> > risk it uses more memory than necessary. The pros for an Iterator is to
> > be able to stream the data without holding the whole structure in
> > memory. I don't know if that makes a real difference for your use case.
> > An Iterable than can only be iterated once is another solution.
>
> An Iterable returns only an Iterator, no need to keep anything in memory
> except of an (anonymous) Iterable instance.
>
>
+1.  I program to Iterable as often as possible.  If iteration is all that
is needed, then... um, it's all that is needed.  ;)

Matt


> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message