GitHub user mdedetrich added a comment to the discussion: Stream JavaDSL: start adding alternate methods that use Java function interfaces instead of the Pekko ones
Java is also being used at the company where I work, lombok is never used there (in fact I haven't seen lombok used in any modern java codebases). This is such a small issue though, while a beginner may be confused about `org.apache.pekko.japi.function.*`, this confusion should be temporary and its also justified. If you want to blame anyone for the confusion you should blame the JDK dev's, they should have supplied `@FunctionalInterface`'s that allow throwing exceptions. Pekko is forced to do things like put allocation of resources into a lambda/function because it has to be evaluated on demand (since streams are lazy) and JDK doesn't provide a nice way of doing this and Pekko is not the only Java API that has to deal with this. GitHub link: https://github.com/apache/incubator-pekko/discussions/960#discussioncomment-8141105 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
