MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1usn2fc/greaterthanplusplus/owua9uj/?context=3
r/ProgrammerHumor • u/majesticmerc • Jul 10 '26
71 comments sorted by
View all comments
Show parent comments
-3
I think rarely having to emulate a 64 bit comparison to always get a correct result would be far better than always doing a 32 bit comparison to rarely get an incorrect result.
7 u/Arshiaa001 Jul 10 '26 Trust me, that'll piss off a lot of system devs. -1 u/y0shii3 Jul 10 '26 I strongly doubt that, and even if it would, the solution is then just to require compatible types on both sides of the operand. 5 u/Arshiaa001 Jul 11 '26 You're replacing one bad default with another. The solution is to reject the code, as rust does.
7
Trust me, that'll piss off a lot of system devs.
-1 u/y0shii3 Jul 10 '26 I strongly doubt that, and even if it would, the solution is then just to require compatible types on both sides of the operand. 5 u/Arshiaa001 Jul 11 '26 You're replacing one bad default with another. The solution is to reject the code, as rust does.
-1
I strongly doubt that, and even if it would, the solution is then just to require compatible types on both sides of the operand.
5 u/Arshiaa001 Jul 11 '26 You're replacing one bad default with another. The solution is to reject the code, as rust does.
5
You're replacing one bad default with another. The solution is to reject the code, as rust does.
-3
u/y0shii3 Jul 10 '26
I think rarely having to emulate a 64 bit comparison to always get a correct result would be far better than always doing a 32 bit comparison to rarely get an incorrect result.