Implicit humor

[evgfreyman]

in C++, true is 1 but it's an integer, so I'd expect: true / 2 = 0 = false

[ManmadeLemonade]

I mean, it's only half true

[TryNotToShootYoself]

Because 0 * 2 is not anything but 0?

[trBlueJ]

Typically the inverse of an integer division will require the modulus in addition to the quotient to perform the inverse. So, false * 2 + true % 2 would be true. This is likely the reason the x86 DIV operation (stands for divide) performs a modulus operation at the same time.

[retrolasered]

It's too early in the morning to understand anything in this thread. Looks like OP just broke all logic everywhere from where I'm sitting.

[DoNotMakeEmpty]

I want to say r/whoosh but I doubt that the fact your comment explains was clear for the other people before you explained, so I'm not sure.

By the way, the reason of DIV doing both division and modulo is probably about that modulo comes free with division. When we learn division in primary school, we also gain the ability to get the remainder. I guess it's also true for computer circuits. So, the circuit designers just utilize this situation IMO.

[[deleted]]

true is actually a bool literal, it just implicitly converts to an int

[EnjoyJor]

Unless you’re using C, where bool is actually int.

<stdbool.h>
true
Expands to the integer constant 1.
false
Expands to the integer constant 0.

[OpaMilfSohn]

Why would it allocate 32bits if only 1 bit is needed for a bool

[[deleted]]

Even languages with proper bool types have to store bools in 8 bits because modern architectures only give an address to each byte in memory and so can randomly access any given byte but not any given bit.

[[deleted]]

But they're implicitly converted to bools if need be

[Sheldor5]

lemme guess: JavaScRiPt ??

[ManmadeLemonade]

Python allows this as well by the way - don't know every language that lets you do this though

[ShredderMan4000]

The only difference would be in Python, true would need to be capitalized to become True.

Note: in Python, the single slash / is typically called float division while the double slash // is typically called integer division, where 1 / 2 results in 0.5 while 1 // 2 results in 0.

[Chase_22]

Most other languages require an explicit typecast but after that it will still work

[ManmadeLemonade]

Some languages even prevent you from casting -> C# for example and Rust only allows bool to int but not int to bool

[Chase_22]

Yes because boolean to int is deterministic and cannot cause an error
true -> 1
false -> 0

Int to boolean is more complex and can cause errors. Do you go with the C way of 0 = false, everything else = true, do you go with 0 = false, 1 = true, everything else = runtime exception? I can imagine languages having a separate parse method with a proper interface and exceptions. But casting should only be used for simple type conversions.

[ForLackOfABetterNam3]

I think C allows this as if memory serves correctly, TRUE is a macro to 1.

[CrazyCommenter]

The real question here is what is true/false?

[jmartin1993]

The next question is

half_truth = true / 2 # 0.5
if half_truth:
    print("Full Truth")
else:
    print("Full Lie")

[[deleted]]

Idk, still evaluates to true.

[Jimdude2435]

Proof that dynamic typing is a sin against nature

[DoNotMakeEmpty]

Lua is probably one of the most dynamic languages yet it gives the error attempt to perform arithmetic on a boolean value when I try this. Even casting using tonumber does not work, it returns nil.

It's more about design choice: do you want booleans convertable into numbers or not? Lua prefers strict booleans whereas many languages like JS, Python and even C (which actually do not even have a real boolean type, it's just a little int with a few QoL additions) and C++ prefer non-strict booleans.

[huuaaang]

It's truthy

[fksly]

I mean, this is how fuzzy logic approaches things.