deleted by creator
deleted by creator
There’s plenty of blame to go around for that one. Trump and The Heritage Foundation also played key roles.
For an application? Never. I’d still use it for something very small like a build script where the hassle of separate compile and run stages makes the whole thing a hassle to use. That might change now, though, since I think Node has gained the ability to execute Typescript directly.
I think a better solution would be to add a method called something like ulock that does a combined lock and unwrap.
My concern with lock+unwrap is only partly because of convenience; I also didn’t like it because I think it’s a bad idea to get people used to casually calling unwrap, because it tends to hide inadequate error handing.
Now that I think about it, I don’t like how unwrap can signal either “I know this can’t fail”, “the possible error states are too rare to care about” or “I can’t be bothered with real error handing right now”. In one or two of those cases you want to leave it in my production code, and in the last you want to audit all instances and replace them with proper error handing. Using the same function for all three cases makes that difficult.
Typescript and JavaScript are different languages and the distinction is important, especially because the two are used in conjunction with each other.
I think a lot of people have decided Dick Cheney was the main person responsible for the W administration’s crimes.
The only Ohioans I know are ones who escaped to Washington, and they’re so glad to be out. Pretty much the same as my view on escaping from Texas.
We need to stop giving handouts to Republicans.
Journalists have been talking about how we need to understand them for 8 years now. What more is there to understand beyond what’s common knowledge already? They’re extremely gullible and most of them are extremely racist and uneducated. Some of them think they’ll benefit from Trump’s tax policies.
try_lock
already exists; it’s called lock
. I just want a more convenient name and I want the name of the new method to be lock
, but that ship has sailed.
My point is that the author clearly likes Harris and doesn’t like Trump.
Nobody who likes Trump is worth listening to. Nobody.
I recommend disengaging immediately whenever they start to talk about politics. Hang up the phone, leave the room, etc. Tell them you won’t discuss politics with them, but other than that, don’t say a single word to them on any other topic until they agree to quit doing it. Rinse and repeat.
I think them kicking you out over politics is, by itself, a good reason to go no-contact with them.
Conspiracy theories. Actual conspiracies are a lot more mundane.
I used to think the they were fun until so many people started taking them seriously. Republicans ruin everything.
He can’t be forced to serve but it may be too late to get his name off of ballots. I’m pretty sure the rules for that vary by state, though. We’ve already then through this once this year with RFK.
Looks like the author missed my main complaint about Rust mutexes, which is that the lock
method returns a Result
. There should be a try_unlock
method for when someone actually wants to handle the rather obscure failure case, and the name lock
should be used for a method that panics on failure but returns a value that doesn’t need to be unwrapped first. I see the current arrangement as being about as sensible as having array subscripting return a Result
to handle the case of a failed bounds check.
Why would he snort Sudafed when he had access to real drugs? Sudafed can act as a simulant but it’s a very rough “high”, more comparable to drinking too much coffee than a party drug.
In absolute terms, it would be a great reason not to elect him. In relative terms, he’s so awful that it’s very far down the list of reasons he’s unfit to serve.
What do you find block-worthy about this post?
It doesn’t even require AI, just lies that fit their crazy preconceptions.