-
Notifications
You must be signed in to change notification settings - Fork 207
[Incremental] Next step towards cross-module incremental dependencies #468
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
Now that external dependencies and incremental external dependencies are one and the same, we need to serialize the fingerprints that may or may not be attached to them. # Conflicts: # Sources/SwiftDriver/IncrementalCompilation/ModuleDependencyGraph.swift
@swift-ci please test |
try Bitcode.read(stream: data, using: &visitor) | ||
} | ||
} | ||
catch ReadError.swiftModuleHasNoDependencies { |
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.
Shouldn't we catch every kind of error here? Like, if more than the signature were to be corrupted and the visitor were to detect it, we should just say the graph is busted and start over.
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.
I don't think so. This covers the special case of getting an external-dep with a fingerprint, but in the meantime the vendor has been compiled without the flag. But maybe I don't follow; we can discuss offline.
return integrate(sourceGraph: sourceGraph) | ||
} | ||
|
||
public func integrate(sourceGraph: SourceFileDependencyGraph) -> Set<Node>? { |
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.
This is a fantastic cleanup
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.
thanks!
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.
Just one question, but it's not enough to hold back integrating this PR.
@swift-ci please test macos platform |
⛵ |
Lots of restructuring; passes the lit tests.