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

Lambda support #5

Closed
VaneskaSousa opened this issue Apr 16, 2020 · 2 comments
Closed

Lambda support #5

VaneskaSousa opened this issue Apr 16, 2020 · 2 comments
Assignees
Labels
feature New feature or request

Comments

@VaneskaSousa
Copy link
Collaborator

It is essential to use lambda so that I can run embedded applications while consuming as little memory as possible. In addition to avoiding bugs caused by the way TotalCross handles retrolambda / lambda

@VaneskaSousa VaneskaSousa added the feature New feature or request label Apr 16, 2020
@jeffque
Copy link
Collaborator

jeffque commented Jun 26, 2020

What bugs in retrolambda?

I use it extensively, and I shall say that the only issues I had with it are:

  1. junit tests
  2. when on a Maven Reactor, the lambda classes deploys to a random JAR file that may or may not be picked up by tc-compiler-help (Running retrolambda mojo in a pom reactor yields lambda classes in wrong target luontola/retrolambda#156, but I need to get the minimum example up and running and open a new issue about that)

Besides that, no problems.

Also, it would be useful if you let @luontola aware of your issues, preferable opening issues at luontola/retrolambda repo

@ItaloYeltsin
Copy link
Contributor

For now I think we should wait the users to open a issue related to this. In the past we had some problems with retrolambda because of the way it was being called in the totalcross-maven-plugin. Currently, users have not complaning about any issues related to retrolambda!

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

No branches or pull requests

3 participants