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

deprecation warning for view bounds under -Xfuture #7629

Closed
scabug opened this issue Jul 1, 2013 · 13 comments

Comments

Projects
None yet
2 participants
@scabug
Copy link

commented Jul 1, 2013

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:

  • writing a mini guide which includes rationale for deprecating view bounds and outlines migration strategies (examples discussed in this thread are a good start)
  • write a code which warns about view bounds being used
  • migrate our own code base so we don't have new deprecation warnings when compiling the library and the compiler
  • update the spec

Mailing list: https://groups.google.com/d/topic/scala-internals/hNow9MvAi6Q/discussion

@scabug

This comment has been minimized.

Copy link
Author

commented Jul 1, 2013

Imported From: https://issues.scala-lang.org/browse/SI-7629?orig=1
Reporter: @soc
Affected Versions: 2.11.0-M7

@scabug

This comment has been minimized.

Copy link
Author

commented Aug 19, 2013

@scabug

This comment has been minimized.

Copy link
Author

commented Aug 20, 2013

@soc said:
I'll have a look at it as soon as I'm done with all the other things needing deprecation/removal.

It feels like the amount of deprecations/removals is increasing from release to release ... not sure whether this is good or bad.

@scabug

This comment has been minimized.

Copy link
Author

commented Aug 20, 2013

@SethTisue said:
it's good.

@scabug

This comment has been minimized.

Copy link
Author

commented Aug 20, 2013

@soc said:
But where will this end?

@scabug

This comment has been minimized.

Copy link
Author

commented Aug 20, 2013

@SethTisue said:
with the language in a better place.

@scabug

This comment has been minimized.

Copy link
Author

commented Aug 20, 2013

@soc said:
I hope so, I hope so.

Small parser hack: https://groups.google.com/d/msg/scala-internals/hNow9MvAi6Q/R8ZgSBunbf0J
Question about Scala IDE quick fix for migrating view bounds to implicits: https://groups.google.com/forum/#!topic/scala-ide-dev/3aBzKPDJnlU

@scabug

This comment has been minimized.

Copy link
Author

commented Aug 26, 2013

@ghik said:
The following idea should probably be in the scala-internals thread, but since I'm far away from being a Scala committer I decided to post this here.
In advance, please forgive me any potential ignorance or lack of some fundamental knowledge if this idea is stupid.

In the scala-internals thread, Adriaan proposed a replacement for view bounds:

Given `class Has[To] { type Conversion[From] = From => To }`

`def foo[T <% Int](x: T) = (x: Int)`

can be rewritten to:

`def foo[T: Has[Int]#Conversion](x: T) = (x: Int)`

I think this could look a lot nicer if Scala had multiple type parameter lists:

Having: `type HasConvTo[To][From] = (From => To)`

`def foo[T <% Int](x: T) = (x: Int)`

can be rewritten to:

`def foo[T: HasConvTo[Int]](x: T) = (x: Int)`

Maybe this could be a good motivation for implementing multiple type parameter lists?

@scabug

This comment has been minimized.

Copy link
Author

commented Aug 26, 2013

@adriaanm said:
Hi Roman -- you're very welcome to post messages like this on scala-internals!
I agree it would be awesome to have multi-type-parameter lists. We just haven't had time to spec and implement them.

@scabug

This comment has been minimized.

Copy link
Author

commented Feb 10, 2014

@soc said:
Also, "why 2.12"? The change is already in, pending IDE support.

@scabug

This comment has been minimized.

Copy link
Author

commented Feb 10, 2014

@adriaanm said:
Collateral of bulk change, sorry. Maybe we should have separate tickets for compiler and IDE support? When dealing with 100s of tickets, these kind of exceptions are hard to deal with.

@scabug

This comment has been minimized.

Copy link
Author

commented Feb 16, 2014

@adriaanm said:
Closing because warning introduced under -Xfuture by scala/scala#2909

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.

@scabug scabug closed this Feb 16, 2014

@scabug

This comment has been minimized.

Copy link
Author

commented Mar 6, 2014

Shiva Wu (shivawu) said:
Really awesome idea of Roman's to have the multiple type parameters, and I think it should be called curried type parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.