-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Sema] Extract @autoclosure diagnostics from type resolver #22348
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
Conversation
@swift-ci please smoke test |
Since @autoclosure attribute is associated with declarations it makes more sense to move diagnostics to where type of the parameter has been completely resolved. This also helps to support parameters with typealiases pointing to function types without any extra logic in the resolver.
665f9c7
to
7f262a7
Compare
@swift-ci please test |
@swift-ci please test source compatibility |
@swift-ci please smoke test compiler performance |
@DougGregor I think it's okay that we are validating more types here because that's what the intended behavior change is - don't try to fail in type resolver but instead to more checks in |
Ah, and also it wasn't accounting for all of the types which got resolved through use of |
@xedin yeah, that sounds right |
Since @autoclosure attribute is associated with declarations
it makes more sense to move diagnostics to where type of the
parameter has been completely resolved. This also helps to support
parameters with typealiases pointing to function types without
any extra logic in the resolver.