The Year of C++ Successor Languages

Re:The Year of C++ Successor Languages by jstimpfle on Monday January 02, 2023 @09:48AM (#34218410)

Are you saying that "not signaling" has not been shown to be a total maintenance nightmare as well?

Because the only way it is not ever a maintenance nightmare is when you really don't care that function execution could be aborted at any point without any visual clue. And the only way I can see you wouldn't care is when you go 100% in to everything-context managed / RAII or similar. And that again, sorry but I can't be arsed to prematurely rip everything into little pieces like that. It makes for terrible code IMO.

[ Parent | on HN ]

Re:The Year of C++ Successor Languages by mike_hock on Tuesday January 03, 2023 @04:01AM (#34229413)

But you can be "arsed" to write an error handler after almost every single function call?

[ Parent | on HN ]

Re:The Year of C++ Successor Languages by jstimpfle on Tuesday January 03, 2023 @06:36AM (#34230278)

I explained here that I consider having to check many return values to be a smell: https://news.ycombinator.com/item?id=34217251

And from my own experience, no I don't have to check a lot of return values.

[ Parent | on HN ]