Semicolon does not parse in match types

Compiler version

3.0.1

Minimized code

def Choice = (_: Any) match { case Int => Long; case Long => Int } // ok

type Choice[A] = A match { case Int => Long ; case Long => Int } // error

https://scastie.scala-lang.org/popPHRHGRTmfZ9n41Un3fQ

Output

'}' expected, but ';' found

Illegal start of toplevel definition

Expectation

Expected the semicolon to separate match type cases the same as for value matches. Couldn’t find a previous discussion on this, so I assume this is not intended?

[neko-kai]

But maybe the “least surprises” strategy would be to allow it in both cases since we cannot forbid it in the term match case.

I agree, but I was also surprised because I’ve had an intuition that semicolons and newlines were usually interchangeable as separators. The semicolon in a term match being a property of the block and not a separator on its own wasn’t something I thought about.

The idiomatic style is to leave semicolons out in both cases.

I agree, but the reason I’ve tried this is because that’s the only way to write a match in one line in REPL.

[odersky]

I actually can’t verify that, as it looks like the last BlockResult can be preceded by semicolon-terminated statements, but the BlockResult can’t end with a semicolon?

But the BlockResult is itself optional.