-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Drop Legacy Cascading Dependencies From the Frontend #33096
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 test |
|
@swift-ci test source compatibility |
|
@swift-ci test compiler performance |
davidungar
left a comment
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.
Fantastic!
|
@swift-ci smoke test |
|
@swift-ci test compiler performance |
|
These numbers make no sense. No way this PR cuts 90% of wall time alone, we just failed an enormous amount of projects because of infrastructure issues. @swift-ci test compiler performance |
|
@swift-ci smoke test |
df5b907 to
78d5d10
Compare
78d5d10 to
f398501
Compare
Now that the top-level source file is the only dependency source that matters, the only case that matters is when request evaluation enters a primary file. For non-primaries, there will be no corresponding swiftdeps file to emit references into, so we're just wasting time and memory keeping track of anything that happens there. This is only possible after we removed cascading dependencies because unqualified lookups had to be charged to the files they originated in. Now, we charge those lookups to the primary that initiated the request.
f398501 to
4557b69
Compare
|
@swift-ci test |
|
@swift-ci test source compatibility |
|
⛵ |
It's been a long time coming.