>> IMO, the danger of
>> "@dataclass(hash=True)" far overweighs whatever convenience it might
Is there any reason specifying has=True could set frozen=True unless
the user specifically sets frozen=False?
Or is that already the case?
I think the folks that are concerned about this issue are quite right
— most Python users equate immutable and hashable—so the dataclass API
should reflect that.
And this would still make it easy and clear to specify the unusual
(and arguably dangerous) case of:
Python-Dev mailing list