Timeline for Exceptions, error codes and discriminated unions
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 5, 2018 at 12:02 | comment | added | maaartinus | @mcintyre321 Sure, you can add information, but you have to do it manually and it's subject to laziness and forgetting. I guess, in more complicated cases, a stack trace is more helpful. | |
| Jun 5, 2018 at 11:57 | comment | added | maaartinus | @dcorking Edited. Sure, if you ignored the return value, then you know nothing about what problem happened. If you do this with a pure function, it's fine (you just wasted time). | |
| Jun 5, 2018 at 11:54 | history | edited | maaartinus | CC BY-SA 4.0 | added 69 characters in body |
| Jun 5, 2018 at 9:04 | comment | added | mcintyre321 | You can return error info with OneOf by making the returned error object contain useful information e.g. OneOf<SomeSuccess, SomeErrorInfo> where SomeErrorInfo provides details of the error. | |
| Jun 5, 2018 at 6:37 | comment | added | dcorking | +1 but why does OneOf not work with side effects? (I guess it is because it will pass a check if you don't assign the return value, but as I don't know OneOf, nor much C# I am not sure - clarification would improve your answer.) | |
| Jun 4, 2018 at 14:23 | history | answered | maaartinus | CC BY-SA 4.0 |