-
Notifications
You must be signed in to change notification settings - Fork 3.1k
[indylambda] Improve test coverage #4609
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
Conversation
Adding tests for the selective use of boxing bridge methods and to show that specialization is not subverted by indylambda. Other aspects of indylambda are tested by tests like: - run/lambda-serialization.scala - run/indylambda-boxing When those tests were written, they only tested the old backend. However, now that we have Java 8 and the new backend avaialble by default to partest, they provide the intended coverage.
|
Review by @SethTisue or @lrytz |
|
see also #4603 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need some more boilerplate: the class needs to extend ClearAfterClass, and ClearAfterClass.stateToClear needs to be set. Maybe this can be improved..
class IndyLambdaTest extends ClearAfterClass {
ClearAfterClass.stateToClear = IndyLambdaTest
...
|
otherwise, LGTM |
|
(admin note: please don't start your comment with LGTM until it's actually good to merge -- at some point the bot will start merging PRs as soon as the reviewer signs off, so may as well get into this habit now) |
|
I'm going to push this to M3, since all other M2 PRs have been merged and this can wait. |
- Add requisite boilerplate for test cleanup to IndyLambdaTest - ... and to the spot where I copy/pasted the wrong code from - Fix comment.
|
@lrytz I've addressed your comments. |
|
LGTM |
[indylambda] Improve test coverage
Adding tests for the selective use of boxing bridge methods
and to show that specialization is not subverted by indylambda.
Other aspects of indylambda are tested by tests like:
When those tests were written, they only tested the old backend.
However, now that we have Java 8 and the new backend avaialble
by default to partest, they provide the intended coverage.