Raymond Hettinger <raymond.hettin...@gmail.com> added the comment:
I intend to make a python-dev post about this so we can decide whether to move forward or not. For now, here are a few thoughts: * Something like this was implemented for strings as an effort to mitigate the harm from a common mistake of using chained addition to build-up string rather than using string join. IIRC, there as a decision at that time not to do something similar for other containers. * FWIW, the non-operator versions of these operations already support passing in multiple arguments and is the preferred way to do it. * I think this PR would help some code in the wild. But typically, people know that building series of new containers will tend to make copies. It would be surprising if it didn't. * We really don't want people to rely on this optimization. It is very fragile. If someone ever adds an extra reference, the chained operations become quadratic again. Right now, I'm -0 on the change. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue36229> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
