Comment by hulitu
3 hours ago
> than it is to design a language that does not require you to jump through hoops to get something correct to compile.
They are doing the same to C. With gcc 15 all warnings are treated as errors.
3 hours ago
> than it is to design a language that does not require you to jump through hoops to get something correct to compile.
They are doing the same to C. With gcc 15 all warnings are treated as errors.
-Wall/-Werror/-Wextra have existed for a long, long time. -Wno-error will still work in gcc15, which quickly defeats the point of werror being a default. If your're writing c/c++ in 2026 and not using wall/werror/wextra, you're actively choosing to compile unreliable code and you should have been jumping through those "hoops" the whole time.
"But, all my dependencies!" Fork them and fix the warnings. Flow the changes back upstream. Use your fork if they're not accepted. Don't buy libraries that compile with warnings, or demand your vendor fix them.
I've been writing c/c++ for a long, long time. The bugs that actually bite you are almost always logical and have little to do with things like a borrow-checker, ask cloudflare.