Adriaan Moors

@smarter, what was the other warning requested in the meeting?

> Is this already decided? No hope for SIP committee to veto it? This issue is meant to be independent of that, because the idea is to limit ourselves to...

https://www.merriam-webster.com/dictionary/eventuality

@smarter suggests we start warning on definition in 2.13, this way library authors can either mark symbolic multi-param methods as `@deprecated` in their library (and thus not get the deprecation...

note that the 2.14 warning shouldn't fire on method that take a single argument list, since those will still be ok in 3.0

the main goal being that the following applications will remain accepted during the whole upgrade (for time-varying reasons) ``` (x, y) :: xs a == (b ,c) ``` the following...

This will need to wait until later in 2.13.x

Definitely!

Yep, whatever mechanism we come up with should support embedded scenarios (as in your [REPL improvement](https://issues.scala-lang.org/browse/SI-9802))

It'll be great to clean this up, but let's be clear that this is not a priority right now.