Timeline for Are exceptions for flow control best practice in Python?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 28, 2023 at 7:40 | comment | added | NeilG |
Says "I found no official written documentation to support [explicit Exception use for flow control]", then immediately quotes the peak explicit baldly obvious official endorsement of EAFP and Exception use for flow control. Then calls it "vaguely relevant". I don't really feel like reading any further.
|
|
| Jun 5, 2023 at 1:29 | comment | added | wtr | I love this answer; thank you for providing it! The handling of a long blast radius reminds me of "function coloring" from async / sync functions in JS ( blainehansen.me/post/red-blue-functions-are-actually-good ). I have some insights not covered in these answers that I might like to add as well. | |
| Dec 31, 2021 at 11:45 | comment | added | Ido Ran | This is your opinion, and I do not agree with most of it. I think there is big difference between return a value and throw an exception. You can do everything with both, I think it's more question of how maintainable the code will be. You can return multiple items, just use a struct/class/array. | |
| Mar 25, 2021 at 2:40 | history | answered | RayLuo | CC BY-SA 4.0 |