-
Notifications
You must be signed in to change notification settings - Fork 10.5k
AST: Rename TypeRefinementContext to AvailabilityScope #77563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AST: Rename TypeRefinementContext to AvailabilityScope #77563
Conversation
@swift-ci please smoke test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool!
@@ -1336,9 +1336,9 @@ def dump_scope_maps : Separate<["-"], "dump-scope-maps">, | |||
MetaVarName<"<expanded-or-list-of-line:column>">, | |||
ModeOpt, | |||
Flags<[FrontendOption, NoInteractiveOption, DoesNotAffectIncrementalBuild]>; | |||
def dump_type_refinement_contexts : |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also update Options.swift
in swift-driver.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ef7be10
to
67c5927
Compare
@swift-ci please smoke test |
Aligned with swiftlang/swift#77563.
Aligned with swiftlang/swift#77563.
Clarify the role
TypeRefinementContext
by renaming it toAvailabilityScope
. There are a few reasons for doing this, despite the churn:TypeRefinementContext
is a fairly broad name that doesn't provide much of a hint about the primary purpose of this structure for most contributors. HavingAvailability
in the name is clarifying.AvailabilityScope
is evocative ofASTScope
, which is useful because the two represent very similar concepts and have similar structures.