When you say user, you mean a user of a function? In that case PHP would throw a TypeError, and presumably only happens when developing/testing.
If you mean in production, like when submitting a form, an Exception may be thrown. In which case you catch it and return some error message to the user saying the date string is invalid.
My point is, you won't ever try. You'd only use "weak" variables inside the function you're working on.
It's explicit when you absolutely need it to be, when the function is being called and you need to know what arguments to pass and what it'll return
I like it in modern PHP, it's balanced. As strict or as loose as you need in each context.
Typed function parameters, function returns and object properties.
But otherwise I can make a DateTime object become a string and vice-versa, for example.
I don't know if we're discussing semantics. A performance score is attributed, and before the fix their scores were all 166. It doesn't work, as you said. So the consequence is the preferred core being "random", isn't it?
Apparently there's a bug in an AMD's driver. It was supposed to assign processes based on each core's self reported performance, but because of the bug it was random.
This "self reported performance" is based on evaluation done to the cores in the fab process, by AMD. Meaning, due to imperfections some cores are a bit better than others.
Even if I coded the form by hand and that happened, it's on me, not on the programming language.
But I don't, I use a framework which handles all that boilerplate validation for me.