Mind sending him here for the burning?
marcos
Yes, because I also have a Windows installation and use it at work. So yeah, I do think it's unreliable.
He didn't even tell the exact coordinates and depth...
Oh, it can happen when you do calculations with compile-time constants...
But the GP's claim that it's a "frequent" thing is suspect.
(Crashing is also useful when you are writing and-user applications, but you'll probably want .expect like in the meme.)
Vibe-coding is absolutely protecting real programmers from the constant bombardment of wannabe entrepreneurs that just need a tech person to write their idea.
Somehow, 10% of the acronyms reduce to "TLA". Including the very nice self-explanatory "three letter acronym".
Yeah, just to say it more clearly: that kind of thing is why lots of people out there insist that operator overloading is a bad idea.
And yeah, it's a C++ thing that mostly doesn't happen in other languages.
Reminds me of the recent reaction to the director of the Supermen movie, and the people calling the xenophobia "barbaric".
I mean, it's nice when it falls back at the same meaning, but it reaching its antonym is just great.
And so much of that money isn’t real money.
Guess what, a large part is government debit.
And also, WTF, nobody said anything about splatting the money. What are you talking abut?
You really need to get your fact together again.
Globally:
Focused on the US:
https://www.snopes.com/news/2023/04/13/728-billionaires-hold-more-wealth/
Well, when you said "we have a deployed branch", you could just have stopped there. All the rest is just what happens after you decide to rename your master branch.
Hum... No it won't.
It's something you only really learn from C or Rust, but your operations will set both to the same list. If you go and change the list, you will change both, but if you set one to a different list, you won't change the other list.
In other words, if you do
list1.push(4)
, you will changelist2
. Butlist1 = [3, 2, 1]
won't.