Probably because it’s what they’re called in C++.
Probably because it’s what they’re called in C++.
But did they do that in Newton’s time?
There’s also a mountain range separating Chile from its neighbors.
Hey, I know that guy! I’m one of his Patreon supporters. It’s weird to see him turn up on the internet at large.
Vulture capitalists.
You’ll be sorry when they’re gone!
Ok, but have they fixed the UI scaling on high-DPI displays?
deleted by creator
But think of the illiterate people! /s
This is the ideal male body. You may not like it, but this is what peak performance looks like.
The midichlorian is the powerhouse of the Force.
Like coriander vs cilantro. Actually that’s the only example I know.
Ironic because poppy seeds have very little flavor and coca literally numbs your tongue.
And being a nightmare to figure out what code is whereas they all communicate independently.
So much this. Especially in a larger company it can be basically impossible to find the code that implements an endpoint, and of course even if you can find it you can’t trace it in a debugger.
The minimum age anyone can do any of these things:
I think that’s currently something like 12 in the US, which is a huge problem.
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.
Yeah, looks like a TILGBBBIPOC flag to me.
Typescript and JavaScript are different languages and the distinction is important, especially because the two are used in conjunction with each other.
Why are we writing new software? There’s plenty already.