Dude, after forcing -std=c++20, the compiler still can’t find a reference for std::ostream::operator<<(float)…
Do I have to link with some non-standard library? There doesn’t seem to have any numbers.a included with gcc.
Dude, after forcing -std=c++20, the compiler still can’t find a reference for std::ostream::operator<<(float)…
Do I have to link with some non-standard library? There doesn’t seem to have any numbers.a included with gcc.


Well, I can assure you that you have requirements.
You just don’t know what they are.
At least NaNs are different from each other and themselves.
SQL’s null would like a word here.
>> typeof(NaN)
<- "number"
It’s valid for C too, but it will be either a double or a float.
for example, simply optimize it away
Yeah, that example makes it reasonable. But the optimizer can do ridiculous stuff when it proves the loop never terminates and also assume it terminates.
The most famous example of UB bullshit is when some compilers run code that is impossible to reach just because there’s an infinite loop on the file (not even in the same function).
Oh, JS’s this is fucked up to many levels above that theoretical issue the language also has.
And that line doesn’t help with the schizophrenia issue.
SQLite doesn’t do highly concurrent tasks. Your life will be much, much better if you don’t even try.
It also doesn’t do Windows shared files, because any access into Windows shared files is highly concurrent on the speeds Windows is able to manage its shares.


The most expensive loses were from mistakes caused by the constant need to react to their attacks, and the most numerous loses were caused by throwing things at their attacks.
And that was enough to make the military look irredeemably incompetent inside the US. Imagine what will happen when they fight an adversary that may actually hit something once or twice. Under a different president, or if they had any non-criminal reason to go into war, the reaction would probably be different, but that’s not the case.


Trump stopped attacking Yemen because they threw enough stuff back that it made the US military look bad. Venezuela is way better armed than Yemen.
The US population expects invincibility, and that doesn’t exist on the real world.
Not deploying the backend doesn’t make it a day off.
The coworker probably got the message right and knows about some integration problem the poster doesn’t know about.
Works better than Teams.
Probably has better privacy and confidentiality options too.


The last plane that was lost due to collision with Venus was wild!


Low code is a real practical way to increase developer productivity. And some of the current tools achieve exactly that already.
Of course, that usually lead to a increase on the number of jobs. The AI people want to believe it will completely replace developers, what can only lead to fewer jobs.
MS can’t force that one to use AI on development. But they can force almost everybody up.
“It doesn’t matter that we are burning 1 trillion dollars with no pat to revenue, because we will create God and it will make money meaningless.”
"Also, it will cure cancer and solve Global Warming. I know dumb people like you that can’t even get a trillion dollars to burn care about those things.
I will never unsee it now… and I’m not even disappointed.


I basically never have this problem on Linux.
I think programs can’t hold removable media busy by default on Debian. If you remove, you lose whatever changes aren’t there. Either way, Linux programs just read files and close them, they mostly don’t keep files open.


Dropbox is lying.
Windows may be lying too, but the only thing certain is that dropbox is lying.
In a high-level, you don’t design them anymore. You write them, in code. The compiler turns your code into the chip masks, and has an optimizer that will mangle the hell out of the relatively simple stuff you wrote.
In a lower level, that compilation is not really done automatically, and people will intervene in lots of places, and AFAIK, how people divide it and interact with it are well guarded secrets from the chip makers.
Oh, that’s right, I was using gcc.