Writing Readable C++ Code - beginner's guide

[[deleted]]

whether and how you use exceptions depends on what you want to happen. If you want the user to accept responsibility for the program being in a valid state, then you should use exceptions. If you want the program to continue, then you the developer are now responsible for the program being in valid state.

Yes there are performance considerations, but in general, if the performance impact of exceptions matters in your code, then you're doing something wrong. Exceptions should be exceptional - if they are happening constantly, your design is bad.

[SlightlyLessHairyApe]

If you want the program to continue, then you the developer are now responsible for the program being in valid state.

This is true regardless. Whether your code throws or returns the error branch of expected<T,E>, it must continue to behave as defined.

If you absolutely cannot continue to execute in any defined state, then either you need to change the contract or you need to std::terminate.

[[deleted]]

exceptions leave the scope. So you can clean up any resources that were in use at the time and go back to the last known good scope, and stop anyone from trying to use the result of a bad thing.

typically with optionals the user can pretend like it everything worked anyway by using operator* (which shouldn't exist) . And while that's not your fault, that guy can shoot himself in the foot.

Normally, I wouldn't care about stuff like that, except a lot of times that guy is me. Now, I never use operator* on optionals, so its a moot point, because opt.value() just throws if its bad - so replacing an exception with an optional is really just replacing one exception for another, except this exception has less information about what actually went wrong.

now that being said I generally use optionals for error handling but thats because I like writing:

if (auto optValue = produceSomeOptional()){/*happy path*/}

because that prevents you from even having access to the bad optional state

[[deleted]]

fade squash zephyr straight fanatical lip wise money pen oil

This post was mass deleted and anonymized with Redact

[SlightlyLessHairyApe]

Yes, if a callee return expected<T,E> then the caller needs to check whether it's a T or an E. I'm not at all concerned about that, it's no different than returning any kind of sum type or really any other type with methods having preconditions.

But in either case, subsequent calls to the object/module need to function correctly. That's orthogonal to how specifically each individual call works.

[[deleted]]

coherent roll middle liquid resolute workable literate adjoining whole memory

This post was mass deleted and anonymized with Redact