Paul, Great job done on the Iterables stuff... I didn't really anticipated a complete removal before the 3.0 release, but...
On Tue, Nov 29, 2016 at 12:19 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > Most (all?) Iterables in Core was replaced before. > > For exceptions, > first of all, I think almost all exceptions in Zest are RuntimeExceptions > and should not cause much problem. For IOException and such, I typically > wrap in UndeclaredThrowableException if the cause/use is unclear and catch > that in the caller. > > Niclas > > On Tue, Nov 29, 2016 at 12:41 AM, Paul Merlin <paulmer...@apache.org> > wrote: > >> Niclas Hedhman a écrit : >> > These two modules and their classes are largely replaced with the Java 8 >> > Stream API already. I will try to get rid of the completely, as the code >> > with Input/Output/Sender/Receiver is significantly more verbose and more >> > complex than equivalent code using the Stream API. >> > >> > I presume no one has any objections to this. >> > >> > Cheers >> >> About zest.functional: >> >> There's something I don't like with our use of Iterables: we have >> multi-iterations and terminal operations spread everywhere. And we don't >> distinguish clearly at which stage things must be collected. >> Replacing Iterables with Streams where no terminal collection is >> required will help. >> I've pushed some changes in that direction. >> >> >> About zest.io: >> >> One thing that Streams don't cope well with out of the box are exceptions. >> We'll have to find a pattern to deal with them. >> >> Cheers >> >> >> >> > > > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
