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.
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.
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.
> 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.
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.
hn at lenardszolnoki dot com