>>>>> "KY" == Ka-Ping Yee <ping@zesty.ca> writes:
KY> It appears that what you are proposing is what interned string
KY> comparison already does (since == checks for pointer equality
KY> first). So, the only observable effect of the change would be
KY> to break all code that tests for type(s) == str.
Shouldn't those already be written as isinstance(s, str)? Maybe with
StringType for str?
Even so, I'm not much in favor of adding more string types to the
language. I think we should be /collapsing/ string types not
proliferating them (i.e. removing the distinction between str and
unicode -- Jython seems to get by just fine that way).
-Barry
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