Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98920
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fischer.name from 62.179.121.155 cause and error)
To: internals@lists.php.net
References: <CAJaRsPsfWtKbke8VvM-na=vCm0E6T62gmamj2V8sJiHRFB7FLQ@mail.gmail.com>
 <c34c89e3-41d7-afd0-e41a-34d037471603@fischer.name>
 <CAESVnVogVsYTUvyOt3_nDPMNR8jeyt2vvV=RByJ1C9FP1nVOZQ@mail.gmail.com>
 <398456D8-170A-4629-B6FF-D64F6DDB9C9A@gmail.com>
 <CAESVnVqWHD6mf6oxO9n+WcaMCXOJWfob=ikKNGy-v4KwnGoz-A@mail.gmail.com>
 <5B258485-B7EE-4DCD-B93F-B036E9B6D4CC@gmail.com>
 <CAESVnVpHG-V_ggzyJw7k+-3gYHwnogcFKDfkuXuefmdjKm3Cmw@mail.gmail.com>
 <8F7D0233-DB1A-4617-8E92-C1719D4D385D@gmail.com>
 <CAESVnVq-gF2M-She6Rpp2_PVNX+EWaHUEb3xcZt24-q96Njvyg@mail.gmail.com>
Message-ID: <efef51b2-0bb9-71bd-f7b1-e7bf0b649318@fischer.name>
Date: Sun, 30 Apr 2017 20:56:03 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0)
 Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAESVnVq-gF2M-She6Rpp2_PVNX+EWaHUEb3xcZt24-q96Njvyg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam_score: -2.9
X-Spam_score_int: -28
X-Spam_bar: --
X-Spam_report: Spam detection software, running on the system "scanner01.home", has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 the administrator of that system for details.
 
 Content preview:  Hi, On 29.04.17 17:53, Sara Golemon wrote: > 1. If the parameter
    isn't reflectable, then it shouldn't be subject to > enforcement. > This
   argument holds no water because internal functions can only > reflect array
    or object type hints, yet we enforce other types > routinely. [...] 
 
 Content analysis details:   (-2.9 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                             [score: 0.0000]
Subject: Re: [PHP-DEV] [RFC] Enable strict_types checking for curl_setopt()
From: markus@fischer.name (Markus Fischer)

Hi,

On 29.04.17 17:53, Sara Golemon wrote:
> 1. If the parameter isn't reflectable, then it shouldn't be subject to
> enforcement.
> This argument holds no water because internal functions can only
> reflect array or object type hints, yet we enforce other types
> routinely.

I selected unfortunate words and wanted to mention reflection as an 
example (in retrospect a bad and confusing one), but would I really 
meant was the "user readable / visible" contract of the function 
definition, as in: "you look at it and know what to expect what it accepts".

I've read through the thread and see your arguments but, to me, the fact 
that this is "nested hidden" in the data structure passed to the 
function still doesn't want me to have this dependent on the strict 
types. I feel that strict types is misused here.

regards,
- Markus