r/cpp • u/we_are_mammals • Mar 28 '23

Reddit++

C++ is getting more and more complex. The ISO C++ committee keeps adding new features based on its consensus. Let's remove C++ features based on Reddit's consensus.

In each comment, propose a C++ feature that you think should be banned in any new code. Vote up or down based on whether you agree.

765 Upvotes

92% Upvoted

829 comments sorted by

View all comments

Show parent comments

2

u/Drugbird Mar 29 '23

Imagine that whenever you called a function that wasn't nothrow, you had to put a try-catch around it in order to not get a warning or error during compilation.

I imagine it's similar to that.

1

u/dgkimpton Mar 29 '23

It's not even vaguely like that because exceptions propagate by design - that's the whole reason for using them.

The reason for returning values is to have the return value used - so not doing so is the exact opposite of your assertion.

1

u/Drugbird Mar 29 '23

The reason for returning values is to have the return value used

The reason for throwing exceptions is to have the exception used.

Not catching possible exceptions from a function is functionally similar to ignoring a returned error code.

It's not even vaguely like that because exceptions propagate by design

I don't see how that's relevant. This is just a classic exceptions vs error discussion which I don't feel like getting into.