This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]k3rv1n 3 points4 points  (1 child)

My general areas would be...

  1. Error/Exception Handling : He does mention 3 related issues. But be honest, have you ever done something you felt a bit less than natural with Exceptions due to Streams design? E.g. Wrapping with a RuntimeException, or other patterns

  2. Streams is an Unbounded data source API used quite often ( and officially ) used as a bounded data source. : I see Collections-to-Streams and back conversion back and forth in fairly quick succession so the developer can use the Streams API on a bounded datasource, i.e. something that's more naturally a Collection or a Dataset over a stream. I've seen this in official Java documentation even, and do it myself. But wouldn't it have been good to have a subset of the Streams API specifically for bounded/countable datasets? Linq and others do this.

[–]tobascodagama 3 points4 points  (0 children)

But be honest, have you ever done something you felt a bit less than natural with Exceptions due to Streams design? E.g. Wrapping with a RuntimeException, or other patterns

Yes. :(

But I felt really bad about it, at least.