News for hackers. Stuff that matters.

A comment on Initialization in C++ is bonkers (2017). Parent comment

Re:Initialization in C++ is bonkers (2017) by motorest on Friday May 16, 2025 @07:15AM (#44003964)
> (Safe) Rust does guarantee to identify uninitialised variable reads (...)

That's great. You can get that check on C++ projects by flipping a compiler flag.

Aren't we discussing C++?

[ Parent | on HN ]
Re:Initialization in C++ is bonkers (2017) by loeg on Friday May 16, 2025 @03:53PM (#44009217)
What flag do you have in mind? (To the best of my knowledge, no such flag exists -- unless you're talking about one of the heavily penalized sanitizer modes.)
[ Parent | on HN ]
Re:Initialization in C++ is bonkers (2017) by motorest on Saturday May 17, 2025 @12:58AM (#44012138)
> To the best of my knowledge, no such flag exists

Your knowledge doesn't seem to even reach the point of having googled the topic. If you googled it once, you'd not be commenting it doesn't exist. Hell, you don't even seem to have read the thread, let alone the discussion.

[ Parent | on HN ]
Re:Initialization in C++ is bonkers (2017) by loeg on Saturday May 17, 2025 @12:17PM (#44015309)
Again with the personal attacks.

I'll note that you have failed to name this "obvious" flag that I'm missing.

[ Parent | on HN ]