Oron Port

Let me clarify. If you want function arguments that should not be part of the pattern match, then these should come as a second argument block of the case, IMO....

@mberndt123 Hey Mathias, thank you again for the amendments. We discussed the SIP today and we strive for a more general approach: A case class or enum case will be...

We had a SIP discussion, and we'll vote on it next time, but I was just thinking about it and the specification needs to account for any singleton that is...

> The whole point of -language:strictEquality is to increase type safety I think the point is for *equality*. Pattern matching does not fall under this category beyond reachability concerns, IMO.

> But `equals` is called in pattern matching with constant patterns, so it's an equality test? For the record, strict equality is applied to `==` and not `equals`. I consider...

> Pattern matching uses `==`. It doesn't use `equals`. Proof: https://scastie.scala-lang.org/A0eckzOaRxaygBFoCMiyWA > > ```scala > locally { > val x: Any = 5L > println(x == 5) // true >...

> It has had the semantics of `==` for as long as I've been involved in Scala (around 2.9.0). Probably as far back as the introduction of pattern matching in...

> @bishabosha @KacperFKorban Actually, it seems we will be backporting this change to 3.6.2 (which, despite appearances, is technically considered the first stable version in the 3.6.x line). I don't...

1. The proposal needs to be somewhat self contained. Make sure to fill out all the template. 2. Please discuss pros/cons to https://contributors.scala-lang.org/t/pre-sip-sharp-string-interpolation/5836/50

> Here we have an expected type so it will always work Not always. Only when there is an explicit destination type. Implicit conversions or type-classes are not applicable. Huge...