-
Notifications
You must be signed in to change notification settings - Fork 168
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
Add CheckedConsumer[N] and CheckedFunction[N] and add wrapper methods to Unchecked #225
Comments
Came here to say that. I just had to write .map(envelopeAndPath -> envelopeAndPath.map2(Function1.from(Unchecked.function(Files::newInputStream)))) Expected to find a method allowing this instead: .map(envelopeAndPath -> envelopeAndPath.map2(Unchecked.function1(Files::newInputStream))) or even .map(envelopeAndPath -> envelopeAndPath.map2Unchecked(Files::newInputStream)) |
Thanks for the feedback, @bendem. This will definitely add value when implemented. |
hi @lukaseder & @bendem, could you please have a look at the following PR and let me know if this is what you were after ? Please note though, that for now this has been done for arity of 1. |
Hmm, I'm having a look at this again. I'm not quite sure what's wrong with this, @bendem: .map(envelopeAndPath -> envelopeAndPath.map2(Unchecked.function1(Files::newInputStream)))
Thanks for your suggestion, @patrox. That might be along the lines of what's being discussed here, although I wonder if we cannot just overload the existing Do note that this code is generated, just as a hint before you move on to suggest manual implementations for all degrees 😉 |
@lukaseder yep, I'm aware that other arity methods are generated, so that's why I created just one set for the single arity to show the general idea :) |
@patrox: OK, I see. So, before discussing PRs, let's discuss use-cases. How would you like to use this new feature? |
Yes, my specific problem was fixed by 91e719d. Before that you had to use jool's |
Oh, I see. Thanks for the feedback. I hadn't checked the dates... |
See also: #214 (comment)
The text was updated successfully, but these errors were encountered: