I love that in Swift, data constructors are namespaced under their type constructor. So there's no naked `Some`, but `Option.Some`.
-
Don't think so. I can hardly think of any case where my work plans have been picked up by someone else.
-
-
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?
- 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.