

There are also react devs creating the windows 11 start menu.
There are also react devs creating the windows 11 start menu.
It would not be a solution in ancient Greece/Rome, where a small penis was part of the beauty standard.
Not In My Back Yard
It refers to people generally supportive of things, but not where they live.
Typical topics are energy/transport infrastructure or housing for refugees/homeless people.
At least be fair and cut out the .into()
The humble !!
operator.
Making compostable, non-toxic electronics is hard, so we decided on a harder goal!
Look we already made a robot out of 30% edible parts (hint its not the electronics), if we linearly extrapolate we will have full edible robots in no time.
Also eating search and rescue robots? Because the one thing we need in disaster situations, is for the expensive equipment to be single use.
maybe we removed the last n characters
If you want to have a library that can also be a standalone executable, just put the main function in an extra file and don’t compile that file when using the library as a library.
You could also use the preprocessor to do it similar to python but please don’t.
Just use any build tool, and have two targets, one library and one executable:
LIB_SOURCES = tools.c, stuff.c, more.c
EXE_SOURCES = main.c, $LIB_SOURCES
Edit: added example
They don’t need to understand it, they just need to ask it a question that refers to it and some surrounding algorithmic structure to create the paradox.
A well prepared mathematician, skeptical of the functioning of the oracle devices could speak that question in a few minutes.
They will pay you, what they pay for another employees day.
You are hounded by mathematicians that want to apply the halting problem to the device.
If they ever get through and ask the question, reality breaks.
You also get 1 trillion in cash delivered to the same location.
https://whatif.xkcd.com/111
They all try to come over to your place, even the insects.
Your employers always find out and adjust your hours.
Saturation is a side effect of eating you won’t receive.
That boolean can indicate if it’s a fancy character, that way all ASCII characters are themselves but if the boolean is set it’s something else. We could take the other symbol from a page of codes to fit the users language.
Or we could let true mean that the character is larger, allowing us to transform all of unicode to a format consisting of 8 bits parts.
That requires some form of self describing format and will probably look like a sparse matrix in the end.
It might also introduce spurious data dependencies
Those need to be in the in smallest cache or a register anyway. If they are in registers, a modern, instruction reordering CPU will deal with that fine.
to store a bit you now need to also read the old value of the byte that it’s in.
Many architectures read the cache line on write-miss.
The only cases I can see, where byte sized bools seems better, are either using so few that all fit in one chache line anyways (in which case the performance will be great either way) or if you are repeatedly accessing a bitvector from multiple threads, in which case you should make sure that’s actually what you want to be doing.
C/C++ considers an nonzero number, as your true value but false is only zero. This would allow you to guard against going from true to false via bit flip but not false to true.
Other languages like rust define 0 to be false and 1 to be true and any other bit pattern to be invalid for bools.
Who do you think is better at writing assembly? @harbard@fedia.io or a modern compiler with hundreds of contributors.