Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #17383

Re: Making the case for "typed" lists/iterators in python

From Stefan Behnel <stefan_ml@behnel.de>
Subject Re: Making the case for "typed" lists/iterators in python
Date 2011-12-16 21:16 +0100
References <CAOFbRmL_w4QJaCdP8bo1YOi-u0i=SPtAcV51PsQOTytKhsJFVw@mail.gmail.com> <jcg2av$jck$1@dough.gmane.org> <CAOFbRmJqJ6zF6=PZPbYu=Z013892ck9zWitW4gubV+F29z9uZw@mail.gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.3750.1324066604.27778.python-list@python.org> (permalink)

Show all headers | View raw


Nathan Rice, 16.12.2011 19:51:
> Nothing stops me from implementing it, in fact it is VERY trivial to
> wrap member class methods onto a list subclass, and wrap functions to
> support vectorized behavior.  The problem is that as soon as you hit
> anything outside your code that returns a list or iterator, everything
> gets blown away unless you explicitly wrap the return value, which
> entirely defeats the point.

The point you are trying to make, maybe.

Stefan

PS: note that you top-posted in your reply, you should try to avoid that.

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread


Thread

Re: Making the case for "typed" lists/iterators in python Stefan Behnel <stefan_ml@behnel.de> - 2011-12-16 21:16 +0100

csiph-web