Uploaded image for project: 'Scala Programming Language'
  1. Scala Programming Language
  2. SI-7629

deprecation warning for view bounds under -Xfuture

    Details

      Description

      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

        Attachments

          Activity

          Hide
          moors Adriaan Moors added a comment -

          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.

          Show
          moors Adriaan Moors added a comment - 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.
          Hide
          soc Simon Ochsenreither added a comment -

          Also, "why 2.12"? The change is already in, pending IDE support.

          Show
          soc Simon Ochsenreither added a comment - Also, "why 2.12"? The change is already in, pending IDE support.
          Hide
          moors Adriaan Moors added a comment -

          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.

          Show
          moors Adriaan Moors added a comment - 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.
          Hide
          moors Adriaan Moors added a comment -

          Closing because warning introduced under -Xfuture by https://github.com/scala/scala/pull/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.

          Show
          moors Adriaan Moors added a comment - Closing because warning introduced under -Xfuture by https://github.com/scala/scala/pull/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.
          Hide
          shivawu Shiva Wu added a comment -

          Really awesome idea of Roman's to have the multiple type parameters, and I think it should be called `curried type parameters`.

          Show
          shivawu Shiva Wu added a comment - Really awesome idea of Roman's to have the multiple type parameters, and I think it should be called `curried type parameters`.

            People

            • Assignee:
              soc Simon Ochsenreither
              Reporter:
              soc Simon Ochsenreither
            • Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: