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

Fix #1950 Enable handling value classes when generating lambda #1952

merged 2 commits into from Nov 30, 2020


Copy link

Resolves #1950

This PR fixes the mentioned bug - during 2.12 development and porting logic from scala.js logic for handling value class was not fully implemented.

Copy link

@sjrd sjrd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs a rebase for the test suite. Otherwise LGTM.

@WojciechMazur WojciechMazur merged commit 4598849 into master Nov 30, 2020
@sjrd sjrd deleted the fix/1950_value_class_in_lambda branch November 30, 2020 16:04
ekrich pushed a commit to ekrich/scala-native that referenced this pull request May 21, 2021
…ambda (scala-native#1952)

* Added test case for issue

* Handle value class when generating lambda function
WojciechMazur added a commit to WojciechMazur/scala-native that referenced this pull request Aug 25, 2021
…ambda (scala-native#1952)

* Added test case for issue

* Handle value class when generating lambda function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

org.scalactic.anyvals.NonZeroFloat cannot be cast to java.lang.Float on 2.12
2 participants