Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request: FluentConcurrentIterable #1422

Closed
gissuebot opened this issue Oct 31, 2014 · 2 comments
Closed

feature request: FluentConcurrentIterable #1422

gissuebot opened this issue Oct 31, 2014 · 2 comments

Comments

@gissuebot
Copy link

gissuebot commented Oct 31, 2014

Original issue created by e...@technoparkcorp.com on 2013-05-22 at 07:06 PM


See original post at SO: http://stackoverflow.com/questions/16568993

Would be great to have a multi-threaded utility class similar to FluentIterable, which would do exactly what FluentIterable is doing, but in multiple threads. I'm ready to submit its code together with unit tests (since I already implemented it for my own needs). Let me know what do you think.

@gissuebot
Copy link
Author

Original comment posted by lowasser@google.com on 2013-05-22 at 07:18 PM


I'm sympathetic to this, and I'd definitely like to see your implementation, but:

  • Whatever we do here, JDK8 will do much, much, much better with parallel streams.
  • JDK8's implementation is pretty heavily ForkJoinPool-dependent, and I just don't know if that's strictly necessary to get peak efficiency, or what, and if we'd need JDK7 to approximate that performance.

To be sure, we've done "poor man's substitutes" for JDK features before, specifically including Closer as a substitute for try-with-resources.

If we do pursue this, I'd be hesitant to do it without making it really good, despite the substantial effort that would involve.


Labels: Type-Addition, Package-Collect

@gissuebot
Copy link
Author

Original comment posted by kevinb@google.com on 2013-05-24 at 02:46 PM


The SO poster even says "I think Java 8 streams will do something like this" -- yes, a TON of work has gone into that, and it's in every way what you want, so the question is only "but I want it sooner". We should not spend any time duplicating their effort.


Status: WorkingAsIntended

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant