Yes, that's what I meant -- "afterwards" meaning after the @dataclass decorator is applied. On Mon, Feb 5, 2018 at 11:09 AM, Kirill Balunov <kirillbalunov@gmail.com> wrote:
2018-02-05 20:47 GMT+03:00 Guido van Rossum <guido@python.org>:
If there's going to be an API for it, it should be in the class, not something that mutates the class afterwards.
I apologize and don't want to make unnecessary noise. But the already selected design with decorator @dataclass implies that it will mutate the freshly created class (which in its turn already limits some possibilities), or I've missed something? If you meant that everything should be defined in one place, then I basically understand your desire as the least of two evils.
With kind regards, -gdg
-- --Guido van Rossum (python.org/~guido)