Jon Pretty

I think I found 6 or 7 design mistakes. Each significant enough to outright reject this proposal. But SIP process doesn't apply anyway.

Not to Dotty, it doesn't... but Martin did change the proposal in response to feedback on his PR, so it's not like it was a closed process.

I don't think any changes can fix it. It's not only what it does, but that the whole thing is a confused, sprawling, over-complicated mess.

But it brings much more accessible syntax to something many programmers would not bother to write because it would be too verbose.

Which of the multiple syntax variations? "enum class" isn't shorter and "enum" hardly supports any Scala language "feature", e.g. methods.

enum List[+T] { case Nil; case ::(head: T, tail: List[T]) } vs sealed trait List[+T] case object Nil extends List[T] case class ::[T](hea...

Sorry if I am hijacking the discussion, but if there is still room for change, may I request that we do it the Swift way?

I'm not familiar with Swift, but my guess is that it wouldn't be an exact fit for Scala and the amendments would result in different issues.