Github user ScrapCodes commented on the pull request:
https://github.com/apache/incubator-spark/pull/539#issuecomment-35180854
Hey Matei,
I have already tried that option, trouble is not with types but with
closure cleaner which does getResourceAsStream on a lambda expression and
fails(which has to be fixed incase we chose this path.).
Another problem is with API, for lambda expression we would need Interfaces
with apply and at the moment we have a lot of them as abstract classes with
"call" method. Would it be okay to deprecate it ? Or take the other way
round as to have separate java8 API.
On Sun, Feb 16, 2014 at 5:40 AM, Matei Zaharia
<notificati...@github.com>wrote:
> See also
>
http://docs.oracle.com/javase/tutorial/java/javaOO/lambdaexpressions.html#target-types-and-method-argumentsfor
example.
>
> --
> Reply to this email directly or view it on
GitHub<https://github.com/apache/incubator-spark/pull/539#issuecomment-35172268>
> .
>
--
Prashant
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-post your response.
If your project does not have this feature enabled and wishes so, or if the
feature is enabled but not working, please contact infrastructure at
infrastruct...@apache.org or file a JIRA ticket with INFRA.
