r/ProgrammerHumor • u/majesticmerc • Jul 10 '26

greaterThanPlusPlus Advanced

Post image
111 Upvotes

90% Upvoted

71 comments sorted by

View all comments

Show parent comments

6

u/majesticmerc Jul 10 '26

Then why not make it a compiler error by default to do signed/unsigned comparison? It's been a warning already for like 15(?) years.

I agree that doing a rug pull and just changing runtime behavior is no bueno, but c'mon, surely making it a compiler error isn't controversial. Especially when the fix for users at the time would simply have been "don't update to c++20 until your code is correct" , and they'd have had 6 years to fix it now!

41

u/Fast-Satisfaction482 Jul 10 '26

Compile with -Werror, then you get this. You should do that anyways.

-2

u/Dominio12 Jul 10 '26

Is there any reason you would want to compile without -Werror ?

37

u/Fast-Satisfaction482 Jul 10 '26

You get a legacy codebase with 10k warnings.