Raptor85 :gamedev: on Nostr: nprofile1q…dj2mx nprofile1q…tnwmw nprofile1q…9kksy I disagree, because it's not ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq4yqjkzqkgv4a27egvq5xmh2ravemytg9g5kldqeqfts92uvh90sqkdj2mx (nprofile…j2mx) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqwsgm9l82qt2pxka5arr04pvw62ymczyj47046v766j3xat8dg3sq8tnwmw (nprofile…nwmw) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq7yr7pmc0a3h7a0ykx5d04j0zdc7js0mksy8ht7wvehwpht6wh83q89kksy (nprofile…kksy) I disagree, because it's not JUST math, it's code, having an explicit cast both shows intent and ensures the compiler computes the result using the correct data type/precision. (implicit type conversions even in modern C/C++ generate at minimum a warning)
depending on language too, it's possible that since the left hand operand is a boolean the result will be BOOLEAN, not an int, if not explicit, which would then be implicit converted to an int on the last add
depending on language too, it's possible that since the left hand operand is a boolean the result will be BOOLEAN, not an int, if not explicit, which would then be implicit converted to an int on the last add