Artem Chikin 6a12dc0070 [Dependency Scanning] Have the scanner cache answer queries relevant to current search paths only. ...

The dependency scanner's cache persists across different queries and answering a subsequent query's module lookup with a module not in the query's search path is not correct.

For example, suppose we are looking for a Swift module `Foo` with a set of search paths `SP`.
And dependency scanner cache already contains a module `Foo`, for which we found an interface file at location `L`. If `L`∉`SP`, then we cannot re-use the cached entry because we’d be resolving the scanning query to a filesystem location that the current scanning context is not aware of.

Resolves rdar://81175942

2021-07-30 09:53:04 -07:00

33 KiB

Raw Blame History

View Raw