-
Notifications
You must be signed in to change notification settings - Fork 21
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
deprecation warning for view bounds under -Xfuture #7629
Comments
Imported From: https://issues.scala-lang.org/browse/SI-7629?orig=1 |
@SethTisue said: |
@soc said: It feels like the amount of deprecations/removals is increasing from release to release ... not sure whether this is good or bad. |
@SethTisue said: |
@soc said: |
@SethTisue said: |
@soc said: Small parser hack: https://groups.google.com/d/msg/scala-internals/hNow9MvAi6Q/R8ZgSBunbf0J |
@ghik said: In the scala-internals thread, Adriaan proposed a replacement for view bounds:
I think this could look a lot nicer if Scala had multiple type parameter lists:
Maybe this could be a good motivation for implementing multiple type parameter lists? |
@adriaanm said: |
@soc said: |
@adriaanm said: |
@adriaanm said: Please open separate tickets for the other issues. These huge, long-running issues make it hard to measure our progress, and they also make it tricky to ensure we don't forget anything in the release notes. |
Shiva Wu (shivawu) said: |
We have rather universal agreement on deprecating view bounds. We are missing a person who has time to deal with the whole deprecation process which in this case would include:
Mailing list: https://groups.google.com/d/topic/scala-internals/hNow9MvAi6Q/discussion
The text was updated successfully, but these errors were encountered: