-
Notifications
You must be signed in to change notification settings - Fork 36
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
Remove 1.8 class files warning #2163
Comments
+1 |
1 similar comment
+1 |
Well, I could remove it, but I'd have to replace it with "actually you can't compile to Java 8 bytecode so you can't use default methods" |
Moving to 1.3. |
Huh?! I think we should remove this warning. It's very annoying and useless. |
I agree. Being unable to use default methods is just another interop problem, there’s no need to warn people about it every time they compile anything at all (even if it’s pure Ceylon code). |
Or, y'know, give them an error if and when they try to call a |
I mean, a problem with the current warning is after seeing only about |
Well, I did suggest to change the error message, but nobody answered. |
+1 for eliminating the message. The impression I got from this warning when I first saw it was 180º off - that Ceylon might be stale and lacking momentum. I think it's fine letting folks discover that |
Can we please remove this warning? “Everything should work well, but if not, let us know” sounds like a cover-our-asses statement because we didn’t test whether we work on 8, which isn’t true at all – by now, we’re very sure that everything we support also works on Java 8. A warning that we don’t support lambdas would be more fitting on an |
OK fine. |
Done, halleluia |
🙏 |
Java 7 has reached end of life, and there aren’t any known Java 8-specific issues, so I suggest we remove the following warning:
because it’s now obsolete.
The text was updated successfully, but these errors were encountered: