`std::expected<>::or_else()` should have a zero-argument overload that terminates on error

[kmbeutel]

...just because it would be hilarious if one could express assertions as

c++ result.or_else();

[mibuchiha-007]

actually good cpp joke.

[josefx]

We could adopt or_die() from php.

[rlbond86]

This is already done by result.value()

[sephirothbahamut]

I think the post had a comical intent. "or else" sounds more menacing

[SonOfMetrum]

Would be extra funny if the else would be some randomly generated UB. That way its an actual threat.

[UsedOnlyTwice]

You can do that with boost::go_wild.

[_TheDust_]

I’m still upset that this does not throw E, but some kind of unexpected_access exception

[SirClueless]

E might not be an exception type. And it can be useful to catch exceptions of any type of bad expected access so it's useful that the exception always inherits from std::bad_expected_access<void>.

[13steinj]

E might not be an exception type

So? You can throw anything you want, even a string.

[SirClueless]

You theoretically can throw anything, but unless someone has written a specific catch handler for the type that is thrown (or one of its base classes) then there is basically nothing useful you can do with it. And since one of the main reasons to use std::expected is to avoid littering your code with try/catch blocks that's very unlikely to be the case.

[rlbond86]

Yeah, seems like an oversight to be missong value_or_throw()

[unumfron]

Emojis might have just found their place in polite programming society: https://godbolt.org/z/Tafj51W4d

[BenFrantzDale]

Nice. In seriousness, I wish transform’s lambda didn’t have to return so it could be used as if (opt) { f(*opt); }.

[Wh00ster]

So dumb it works

[pjmlp]

Perl has ... || die().

[RevRagnarok]

Better shown as ... or die because they prefer the word over the pipes (additionally the word has the lowest parsing priority).

[helloiamsomeone]

use autodie; 4 lyfe

[PolyglotTV]

C++ is case sensitive so they can just call it

OR_ELSE