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
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
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.
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.
The Ninja files being that huge is likely more to do with the Android build environment or the tool that generates them. The main advantages of Ninja as a build executor are that the language is simple and it processes the build graph very quickly.
Is the moon not already tidally locked? The same hemisphere of it always faces the earth. Is there a different kind of tidal locking or orbital resonance it will settle into?
Depending on the area of logistics OP is in, it's not unlikely that he'd need on-call engineers for his logistics management system. Blockages in supply chain can be extremely expensive.
Perhaps the "rising tide" takes longer to reach some than others. I hope for a more equitable, fairer future, but it's likely my outlook is somewhat jaded.
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