Re: [RFC] Enable strict_types checking for curl_setopt()
| From: | Sara Golemon | Date: | Mon, 24 Apr 2017 23:55:25 +0000 |
| Subject: | Re: [RFC] Enable strict_types checking for curl_setopt() | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-98867@lists.php.net to get a copy of this message | ||
On Mon, Apr 24, 2017 at 4:09 PM, Stanislav Malyshev <smalyshev@gmail.com> wrote:
> it's clearly
> business logic. Which I have no problem with, but it shouldn't be part
> of type system then.
>
We're certainly arguing semantics at this point. Let's agree that
type enforcement is a good thing (which you seemed to say in your
first response) and move on to how that's implemented.
Why shouldn't we allow the same call-time decision making around
strict/weak enforcement to apply to "business logic" type enforcement
as it does to argument types? Surely consistency is a good thing as
well?
-Sara