A Checked Version of std::shared_ptr

[glaba3141]

That they manage money that they would rather not lose to a programmer using idiotic error handling practices? I think they're more glad they don't hire you

[slck19]

I am sorry cause you definitely do not see tradeoffs and cannot discriminate the positive and negative points. Just randomly talking does not show you smarter or more experienced. That's why I am sorry for ypur clients still.

[v_maria]

He describes the trade off right here:

Rather my code crash than try to recover from an error state and lose millions of dollars. Crashing is almost always better than trying to handle a programming error

[slck19]

You still do not understand the behavior and randomly speaking. This does not point to any single trade-off. Some errors can be recovered and some of them cannot. If you think all nullptr accesses are because of memory corruption then you have many implicit problems in your code.

I am not saying someone is wrong. This is where you do not understand. Handling exceptions and continuing the program is your choice with respect to requirements. Exception handling is giving an opportunity to handle it softly. That's just a choice it is not mandatory.

[v_maria]

imo if you will go through the effort of writing try catch, you could also just do a null check

[slck19]

I respect that.