Friendly reminder for Scala developers: type inference for Option.fold suuuuuuuucks. Hilariously that's b/c it's curried, as you can see ->pic.twitter.com/jj7b2c0bib
-
Well, you're right, probably "strangely" would have been more unambiguous there.
As @contrarivariant says, it's the uncommon case. But the solution is elsewhere: Baz's constructor would be more useful returning a Foo.
-
-
Definitely. Same for Bar's ctor. But then I could not write: val x = Baz("hello") println(s"${x.a}") Not that I wanna do it, just saying. :)
-
Maybe we could propose, as good practice, whenever you have an ADT provide smart ctors in the companion objs returning the parent type. :-)
- 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.