Fix swapped errors for frozen/non-frozen dataclass inheritance #18918
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a mix-up in error messages related to frozen and non-frozen dataclass inheritance.
Currently:
Inheriting a frozen dataclass from a non-frozen one incorrectly gives the error:
Cannot inherit non-frozen dataclass from a frozen one
Inheriting a non-frozen dataclass from a frozen one gives the error:
Cannot inherit frozen dataclass from a non-frozen one
This PR swaps these two error messages and rephrases them for better clarity.