*

1 point by andreamancuso 0 minutes ago | next | edit | delete [–]

Good point, but there’s a key difference between what abstract base classes or protocols enforce and what this proposal aims to do.

- Abstract Base Classes (ABCs) and Protocols help define interfaces and ensure that methods are implemented, but they don't automatically ensure object consistency across the class. They focus on the shape of objects, not the correctness of their internal state over time.

- This proposal for class invariants would enforce state consistency automatically after every method call, regardless of what methods are defined in the class. It’s more about ensuring that the internal state of the object is always valid (like Balance >= 0) without requiring explicit checks after every method.

As for decorators: Yes, they could technically enforce invariants, but the key point here is consistency and minimal friction. Using a decorator still requires you to opt in manually, and can lead to potential mistakes, especially when inheritance or metaclasses are involved. The goal of this proposal is to provide an explicit, built-in way to define and enforce invariants, without needing a decorator for every class or method.