leni536

Abolish copyright then. The selective enforcement needs to stop.

And can these avid readers publish these recited passages without infringing copyright?

This is probably Windows pulling LG software through Windows Update bases in EDID. Linux won't ever do this BS.

And all the train depots and train stations are already covered in solar panels, I presume.

This first became apparent to me when I got a slide rule. Pi is often marked on the various scales and an x^2 scale is often nearby the x scale.

Capillary action is subject to the same limits as suction at the top. Capillary action can't increase the water pressure at the bottom of the tree.

If you put a straight thin capillary tube upright in water so it sucks up water from the bottom, no matter how thin, it can't draw water up above ~10m of water level.

What would you call it?

I am working on it. Floating-point IO is rather heavyweight, so the usual approach of naively slapping constexpr on all the things and putting them in headers can have some observable negative consequences on resource usage during compilation even if you don't use the new constexpr functionality.

To the best of my knowledge fmtlib does implement constexpr formatting for float and double, but not long double.

It trickles down.

One reason to use inline assembly is to use instructions that are basically unknown to the compiler, in which case it can't really tell what is being accessed/modified.

Google and Apple are useless for dmca unless you have a court order.

They deserve to also be sued too for the infringement. I don't think safe-harbor applies if they don't act on a valid notice.

There's no way to verify the integrity of the system, and any malicious app can just grab your banking credentials or enable criminals to unlock and drive away with your car.

I don't see how the second half of the sentence follows from the first half.

GP probably meant "POD for the purpose of layout" in the Itanium ABI. It's not the same as standard layout, and POD is not a term in recent C++ standards.

Linear light (if that really is a term of art).

Depends. Many times a linear colorspace is exactly what you want.

Specified by whom? Not the C standard for sure. It is indeed soecified by individual ABIs, and ABIs don't tend to do anything too weird, but that's another question.

And a last, most sneaky one: At checkout if you pay with credit/debit card don't use Ryanair's "guaranteed exhange rate" if the cost of the flight is not in your card's currency (ticket by default, at least two clicks to find and untick it). That's ~6% gap from mid-market exhange rate, the worst cards do better than that.

Pokémon being used for war efforts is prime South Park material, too bad they already did that.

This is what the typing spec says about type narrowing[1]:

"Type checkers should narrow the types of expressions in certain contexts. This behavior is currently largely unspecified."

Have fun.

[1] https://typing.python.org/en/latest/spec/narrowing.html#type...

It's probably kinda helpful in git blame.

Basically never for 8-bit color channels.

There is no such thing as "Chinese Export".

https://cemarkingassociation.co.uk/latest-news/ce-marking-an...

But surely anything the LLM outputs is clear of licensing requirements /s

Or would Microsoft like to argue otherwise in court?

Implementation-defined without further constraining the behavior is not much better than undefined.

Defining it to always error would add overhead even for proper aligned access on x86, as the generated code would need to explicitly check in many cases.

It honestly surprises me we don't hear news about vim/neovim plugin supply chain attacks.

Unaligned access being fine in one architecture, but not in others would create separate dialects, regardless of being blessed by ISO C.

Just don't do unaligned access, it's a dialect that doesn't exist currently, and should never exist.

Only in C, that one is defined in C++.

edit: I'm not sure it's even undefined in C.

Undefined means that the ISO C doesn't define the behavior. An implementation is free to do so.

How do you compare? What trusted channel do you use to retrieve the real public key?

It's not happening by chance, there is a bug somewhere.

From what I skimmed the package should just call to the js runtime's crypto.randomUUID(). I think it should always be properly seeded.

I think it is extremely unlikely that the runtime has a bug here, but who knows? What js runtime do you use?