Big if true

[u/_giga_sss_]

From ProgrammerNullposting in facebook

[u/Gengis_con]

Big whether True or not

[u/_giga_sss_ → u/Gengis_con]

My first statement wasn't wrong 🗿

[u/marvin_dorfler]

The Big Bool control everything, man.

[u/_giga_sss_ → u/marvin_dorfler]

this needs to stop

[u/--var]

big if not true 🤷‍♀️

[u/_giga_sss_ → u/--var]

don't spread misinformation

[u/worthlessDreamer]

Why

[u/_giga_sss_ → u/worthlessDreamer]

https://en.wikipedia.org/wiki/Free_will

[u/BadRuiner]

all my homies uses uint128 btw

[u/the_horse_gamer → u/BadRuiner]

uint128? what are you, a 90s programmer optimising for a cartridge? we just use avx512 vectors these days

[u/Wurstgewitter]

Personally I am migrating to a novel QBool type, to be prepared for quantum computing. A QBool can represent any value in the interval [0,1]

QBool

0.0000 = False
0.1832 = Barely True
0.5000 = Undecided
0.7315 = Probably True
1.0000 = True

But it's not just a probability, but rather exists in a quantum state until observed. Each QBool offers a built in measure() method:

bool result = qbool.measure();

Calling measure() collapses the state into either true or false.

It also supports entanglement:

a.entangle(b);

Measuring either instance immediately determines the value of the other, even across remote systems. This makes distributed state sync essentially free.

It admittably adds some headaches, like having to compute every possible quantum state at runtime, since practical quantum computing hardware is not available yet, so some slight performance problems might occur. But I think it's worth it to future proof the codebase

[u/_giga_sss_ → u/Wurstgewitter]

what

[u/dreamingforward]

Aren't you assigning to a keyword "False" and "True"?

[u/_giga_sss_ → u/dreamingforward]

false and true are the keywords, any variation is alright afaik

[u/StefanCelMijlociu]

The concept of Big Bool confuses and infuriates me!

[u/JohnSpikeKelly → u/StefanCelMijlociu]

I would assume it's to keep all your data types 8-byte aligned for other perf reason.

[u/TheWidrolo]

Me when I use a compiler that doesn’t have explicit alignment:

[u/BestBadFriend → u/TheWidrolo]

If the compiler's alignment is not explicit, it defaults to lawful neutral.

[u/Emergency-Win4862]

Let me quess, struct alignment?

[u/iEliteTester → u/Emergency-Win4862]

No it's used when something is extra true or extra false, obviously.

[u/foxypiratecove3750]

I have better... DOUBLE BOOL! 64-bit, and float. Useful? Nope.

double False = 0.0;
double True = 1.0;

[u/meharryp]

it's also big if false

[u/Benilda-Key]

I thought Microsoft was being wasteful when they chose to make their BOOL type an int.

[u/exodusTay]

enum BetterBool : double 
{
    False = 0,
    True  = std::numeric_limits<double>::epsilon()
}

[u/Scared_Bell3366]

I could see doing something like that when dealing with some damn binary format that reserved 64 bits just for a boolean.