AST: Remove ProtocolDecl::getSuperclass() #72495
Merged
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.
Cleaning up my own technical debt from 2018.
There are two ways to spell a class-constrained protocol:
The
ProtocolDecl::getSuperclass()
method only handled the first case, returning a null Type in the second case.This remained an issue for as long as it did because most clients would either use the lower-level
getSuperclassDecl()
, which correctly visited the where clause, or they would process requirement signature requirements or whatever.This problem surfaced again because there was a recent regression with the
where Self: C
form because a new call to getSuperclass() was introduced in serialization.Also it turns out all existing other callers of
getSuperclass()
either suffered from the same problem, or were unnecessary. So this PR just removesProtocolDecl::getSuperclass()
.Fixes rdar://problem/124478687.