[spacechild1]

> Exceptions should be reserved for developer errors like edge cases that haven’t been considered or invalid bounds which mistakenly went unchecked.

Isn't this what assertions are for? How would a user even know what exceptions they are supposed to catch?

IMO exceptions are for errors that the caller can handle in a meaningful way. Random programmer errors are not that.

In practice, exceptions are not very different from Result types, they are just a different style of programming. For example, C++ got std::expected because many people either can't or don't want to use exceptions; the use case, however, is pretty much the same.

[tyleo]

I’ve often seen assertions throw exceptions when violated. Users don’t catch exceptions, developers do. Users interact with the software through things like failure pop ups. You’d need to check that there’s a failure to show one, hence returning a Result to represent the success/fail state.

[spacechild1]

With users I meant library users, not end users.

> You’d need to check that there’s a failure to show one

You can do this with either exceptions or Result types. At the end of the day, it is a matter of culture and personal preference.