I love that in Swift, data constructors are namespaced under their type constructor. So there's no naked `Some`, but `Option.Some`.
-
Yep. It's a complete&utter trainwreck. Having made multiple enum impls over the years, I'd have died in shame proposing something like that.
Is the problem that they don't quite offer a complete replacement for sealed traits and case classes?
-
-
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.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.