flqn

It makes it less ductile, which means it's harder and more resistant to deformation. Bronze is more brittle than copper.

Adding fibres to already brittle materials improves their resilience to tensile forces mostly

This is a good change. Potentially ambiguous to read syntax is being made clearer in a way that harms no previous code substantially.

I sometimes wonder if the comments that say nothing more than "C++ is too complicated" are from people who use it regularly, much less people who are even commenting on TFA

What is a teapot?

I cannot make one of those.

Refrigerator.

Can't pass a PhoneNumber to a function expecting an EmailAddress, for one, or mix up the order of arguments in a function that may otherwise just take two or more strings

Dates are unfortunate in that you can only really parse them reliably with a TZDB.

Nitpick: icons are about signifiers, not affordances. A button affords being pressed, an icon on the button signifies what pressing it will do.

In context, binary breakup and binary fracture apppear to mean a splitting ofa whole into two parts along a given line or plane

Since the optimiser is allowed to assume you're not invoking UB, and strlen of null is UB, I don't believe that it would consider that case when optimising this function.

You mean the same problem that the article is trying to solve in C? Generic data structures?

"Just FYI I have a PhD in cosmology" is the credentials for the poster being an expert.

That would certainly catch nearly all migration issues, but it doesn't provide a helpful error message like a test for a specific mistake like this does.

Ideally both approaches would be used, with the general case being used to detect and inform more targeted tests.

And the Greek mathematician is pronounced OY-clid ;)

I think the author misspoke and meant to say "easy-to-misuse" instead, which it definitely was.