On Fri, Jun 2, 2017 at 3:10 PM, Ivan Levkivskyi <levkivskyi at gmail.com> wrote: > On 1 June 2017 at 00:10, Guido van Rossum <guido at python.org> wrote: > >> >> On Wed, May 31, 2017 at 2:16 AM, Ivan Levkivskyi <levkivskyi at gmail.com> >> wrote: >> >>> On 31 May 2017 at 00:58, Guido van Rossum <guido at python.org> wrote: >>> [...] >>> >>> Thank you for very detailed answers! I have practically nothing to add. >>> It seems to me that most of the Kevin's questions stem from unnecessary >>> focus >>> on runtime type checking. Here are two ideas about how to fix this: >>> >>> * Add the word "static" somewhere in the PEP title. >>> >> >> So the title could become "Protocols: Static structural subtyping (duck >> typing)" -- long, but not record-setting. >> > > I am thinking about "Protocols: Structural subtyping (static duck > typing)". The reason is that subtyping is already a mostly static concept > (in contrast to subclassing), > while duck typing is typically associated with the runtime behaviour. > > This might seem minor, but this version of the title sounds much more > naturally to me. > +1 -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170605/d83c2f69/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4