Stephen J. Turnbull writes
> Every feature means making an arbitrary choice that may or may not be
> what the programmers wanted.
I don't think that's what greg meant.
It's not an arbitrary choice between multiple possible features that would
cover the same need.
It's an arbitrary choice that the
There is no need for a whole new syntax for what can trivially be
accomplished by a decorator,
and a simple one, in this cases.
I for one am all for the inclusion of a decorator targeting either the
__init__ method
or the class itself to perform this binding of known arguments to instance
attribut
On 18/04/22 7:29 pm, malmiteria wrote:
It's an arbitrary choice that the C3 feature itself makes, and the programmer
is left guessing what that choice was, unless they can take the time to learn
C3 in depth.
Even if you do, it's still an arbitrary choice to prefer the leftmost
method, which m
On Mon, Apr 18, 2022 at 4:24 PM Joao S. O. Bueno
wrote:
> I for one am all for the inclusion of a decorator targeting either the
> __init__ method
> or the class itself to perform this binding of known arguments to instance
> attributes
> prior to entering __init__. It could live either in functo
malmiteria writes:
> Stephen J. Turnbull writes
> > Every feature means making an arbitrary choice that may or may
> > not be what the programmers wanted.
>
> I don't think that's what greg meant.
I don't either. That's a separate comment that I made about the
nature of developing a produ