Niclas Hedhman a écrit :
> No feedback should be interpreted as either; "Yeah, that is all good,
> nothing to add" or "Community has fallen asleep"
>
> You know that I typically don't sleep... :-) It is all good.
Hehe :) I'll proceed and merge then.
> On Thu, Dec 8, 2016 at 9:47 PM, Paul
No feedback should be interpreted as either; "Yeah, that is all good,
nothing to add" or "Community has fallen asleep"
You know that I typically don't sleep... :-) It is all good.
On Thu, Dec 8, 2016 at 9:47 PM, Paul Merlin wrote:
> Paul Merlin a écrit :
> > Gang,
> >
>
Gang,
I pushed a commit on the replace-io-by-stream branch that replace usage
of core/io with Java 8 Streams:
https://github.com/apache/zest-java/commit/eb4e31a97a92609feb2e7bb18d135de432d511db
After this commit, core/io is completely unused across the whole SDK.
The code is much simpler even
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 wrote:
> Most (all?) Iterables in Core was replaced before.
>
> For exceptions,
> first of all, I
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
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
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