Current hardware trends make C++ exceptions harder to justify

Re:Current hardware trends make C++ exceptions harder to jus... by kllrnohj on Tuesday February 22, 2022 @07:08PM (#30435716)

And it's one for which exceptions are a perfect fit. Even if at the entry point of your "parseJpeg()" function you instead return a variant<result, error>, internally propagating that error via exceptions is the "correct" design. Otherwise you're littering the code with branches, which makes the expected common path slower.

Which the paper covers, that's the std::expected section: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p254...

As a bonus not only is using exceptions for this faster, it's also less error prone. There's much less risk of any intermediate function or helper abstraction failing to propagate an error code properly.

Well, it would be if exceptions weren't avoided like the plague in C++ because they have a, well, bad implementation, which can't be meaningfully fixed without ABI breakges (as the paper covers)

[ Parent | on HN ]

Re:Current hardware trends make C++ exceptions harder to jus... by atq2119 on Wednesday February 23, 2022 @01:19AM (#30438264)

If your service is public facing and therefore subject to DoS attacks, you should design around the error path being fast.

Which really should be possible with exceptions. It's a shame that it isn't.

[ Parent | on HN ]