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


Groups > comp.lang.python > #17383 > unrolled thread

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

Started byStefan Behnel <stefan_ml@behnel.de>
First post2011-12-16 21:16 +0100
Last post2011-12-16 21:16 +0100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

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

FromStefan Behnel <stefan_ml@behnel.de>
Date2011-12-16 21:16 +0100
SubjectRe: Making the case for "typed" lists/iterators in python
Message-ID<mailman.3750.1324066604.27778.python-list@python.org>
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.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web