-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Eval compile error in 2.12.0-RC1: Improvement or regression? #1377
Comments
At the least it seems like a change in inference -- either a a known-change in 2.12 or some kind of bug regression. For our part I don't mind adding the type annotations (it probably makes the code easier to read) but it probably also makes sense reporting upstream to the Scala team. Do you want to do it? If not I'm happy to open one later on. |
@non I very casually mentioned this on gitter scala/contributors. I'm happy to raise an issue on their JIRA later today. I'll post with link when done, so we can track |
Thanks! |
is there a branch that's set up to use 2.12.0-RC1? I'd like to look at this for you, but I don't want to duplicate work you've already done, either |
@SethTisue #1382 uses 2.12.0-RC1. If you compile this locally, please see the note in the PR re local scoverage |
The discussion is on JIRA now, but I just wanted to say thanks for the report. It's enormously helpful to get reports like these. |
@SethTisue and FTR for those that do not look into JIRA - Awesome work!!! Really, I mean it |
reference: typelevel#1377
This is changed and the issue noted in a comment in #1415, so I think we can close this issue once that's merged. |
#1415 is merged |
Compiling
Eval.scala
in 2.12-0-RC1 I get a compile error that is trivial to fix, but nevertheless represents a change as the code is fine in 2.10/2.1. So the question here is whether it is an improvement or a regression that we can highlight.compile:
Trivial fix:
The text was updated successfully, but these errors were encountered: