Re: RFC: Protocol Type Hinting
| From: | Anthony Ferrara | Date: | Wed, 26 Jun 2013 16:24:23 +0000 |
| Subject: | Re: RFC: Protocol Type Hinting | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-67893@lists.php.net to get a copy of this message | ||
All,
I've updated the RFC, renaming "Protocol Type Hinting" to "Structural Type
Hinting" (keeping the name of the file for historical reasons).
I've also expanded out the use-cases with a dedicated section and two
examples (middlewares and third-party specified "standard" interfaces)...
Thoughts?
Anthony
On Wed, Jun 26, 2013 at 11:03 AM, Anthony Ferrara <ircmaxell@gmail.com>wrote:
> Robert,
>
>
> On Wed, Jun 26, 2013 at 10:52 AM, Robert Stoll <rstoll@tutteli.ch> wrote:
>
>> I had a quick look at GO and as far as I understand they do not use duck
>> typing but a structural type system.
>> http://golang.org/doc/faq#implements_interface
>>
>> Please change this in your RFC to avoid misunderstandings.
>
>
> Great idea. I'll update the RFC and code to call it "structural typing"
> instead of protocol. A much better term...
>
> Thanks!
>