[snip]
>I propose `x .= y` -> `x = x . y`, for any `y`. [snip] I think you mean "any y that is a member of x" Also, note that this syntax means that x will be rebound to the result of calling x.y, whatever that is (frequently, None, for mutating methods) In general, you can't count on methods to return references to their instances, even though it's handy for fluent coding, so this side effect may be unexpected to some That's a problem with your original example: >long_name = mkbuilder() >long_name = long_name.seta(a) >long_name = long_name.setb(b) >y = long_name.build() What do the methods seta and setb return? If they don't return "self" you've got a problem. I think. FWIW why can't you just write: x.y or for your example: long_name.seta(a) ?
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/