When building with explicit modules, Swift compilations do not require any of the headers to be present on disk, because the AST contains all the necessary information (save for a bug(?) in canImport which fails if the headers aren't also present). However, other tooling may want to inspect compilation actions and have access to those headers.
This feature is a no-op for implicit module builds, since the headers are always included to begin with, and it is off by default.
PiperOrigin-RevId: 461668350
(cherry picked from commit 81f7b547ff6dea6e67fb0ee4c59e1e5a945cd03d)
When building with explicit modules, Swift compilations do not require any of the headers to be present on disk, because the AST contains all the necessary information (save for a bug(?) in
canImport
which fails if the headers aren't also present). However, other tooling may want to inspect compilation actions and have access to those headers.This feature is a no-op for implicit module builds, since the headers are always included to begin with, and it is off by default.
PiperOrigin-RevId: 461668350 (cherry picked from commit 81f7b547ff6dea6e67fb0ee4c59e1e5a945cd03d)