Timeline for Why use Either over (checked) Exception?
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 31 at 6:51 | review | Close votes | |||
| Nov 5 at 3:01 | |||||
| Oct 30 at 20:28 | answer | added | lexspoon | timeline score: 2 | |
| Jul 14, 2020 at 11:22 | comment | added | Eyal Roth | Related: fsharpforfunandprofit.com/posts/… | |
| Jul 13, 2020 at 20:09 | comment | added | Eyal Roth | Related: softwareengineering.stackexchange.com/questions/150837/… | |
| Jan 5, 2017 at 13:56 | comment | added | Eyal Roth | Seems like the developers at Databricks prefer using exceptions over Either/Try too. This is not a random style guide; that team wrote most of Spark, and the guide is mostly accepted by Martin Odersky. | |
| Sep 10, 2016 at 0:42 | history | edited | Eyal Roth | CC BY-SA 3.0 |
added 1789 characters in body
|
| Sep 9, 2016 at 11:56 | history | edited | gnat | CC BY-SA 3.0 |
redundant tag removed from title
|
| Sep 9, 2016 at 0:05 | history | tweeted | twitter.com/StackProgrammer/status/774035894298746881 | ||
| Sep 8, 2016 at 19:16 | history | edited | Eyal Roth | CC BY-SA 3.0 |
edited body
|
| Sep 8, 2016 at 17:51 | answer | added | Jörg W Mittag | timeline score: 8 | |
| Sep 8, 2016 at 17:19 | answer | added | BobDalgleish | timeline score: 2 | |
| Sep 8, 2016 at 17:17 | answer | added | Karl Bielefeldt | timeline score: 17 | |
| Sep 8, 2016 at 17:14 | comment | added | Robert Harvey | @JörgWMittag: Well, good. That means that you can use it for all of its monadic goodness, and not be particularly bothered by how "clean" the resulting code is (though I suspect that functional-style continuation code would actually be cleaner than the Exception version). | |
| Sep 8, 2016 at 17:12 | comment | added | Jörg W Mittag |
@RobertHarvey: Technically speaking, Either by itself is not a monad. The projection to either the left side or the right side is a monad, but Either by itself isn't. You can make it a monad, by "biasing" it to either the left side or the right side, though. However, then you impart a certain semantic on the both sides of an Either. Scala's Either was originally unbiased, but was biased rather recently, so that nowadays, it is in fact a monad, but the "monadness" is not an inherent property of Either but rather a result of it being biased.
|
|
| Sep 8, 2016 at 16:55 | comment | added | Robert Harvey |
Either looks like a monad to me. Use it when you need the functional composition benefits that monads provide. Or, maybe not.
|
|
| Sep 8, 2016 at 16:42 | comment | added | Eyal Roth |
@RobertHarvey Seems like most of the article discusses Try. The part about Either vs Exception merely states that Eithers should be used when the other case of the method is "non-exceptional". First, this is a very, very vague definition imho. Second, is it really worth the syntax penalty? I mean, I really wouldn't mind using Eithers if it weren't for the syntax overhead they present.
|
|
| Sep 8, 2016 at 16:24 | comment | added | Robert Harvey | Read this: mauricio.github.io/2014/02/17/… | |
| Sep 8, 2016 at 16:14 | history | asked | Eyal Roth | CC BY-SA 3.0 |