Guido van Rossum wrote: > I've now looked at asciistr. (Thanks Glenn and Ethan for the link.) > > Now that I (hopefully) understand it, I'm worried that a text > processing algorithm that uses asciistr might under hard-to-predict > circumstances (such as when the arguments contain nothing of interest > to the algorithm) might return an asciistr instance instead of a str > or bytes instance, It seems to me that any algorithm with that property has a genuine ambiguity as to what it should return in that case. Arguably, returning an asciistr would be the *right* thing to do, because that would allow it to be used as a component of a larger algorithm that was polymorphic with respect to text/bytes. -- Greg
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