Do not print package-name in non-package interface by default.

Having package-name printed in public or private interface led to strange dependency errors in the past. For example, an SPI module is a dependency within a package, but due to the package-name being printed in public or private interface, dependency scanner tries to find it even for an external client of the package, causing a `no such module found` error. The  -disable-print-package-name-for-non-package flag helps with such case, but to enforce the correct behavior, we should make it a default to not print package-name in public or private interface.

Resolves rdar://135260270
This commit is contained in:
elsh
2024-09-04 02:36:16 -07:00
parent 2b817f377d
commit 640b1252fc
4 changed files with 10 additions and 11 deletions

View File

@@ -70,10 +70,6 @@ struct ModuleInterfaceOptions {
/// Print imports that are missing from the source and used in API.
bool PrintMissingImports = true;
/// If true, package-name flag is not printed in either public or private
/// interface file.
bool DisablePackageNameForNonPackageInterface = false;
/// Intentionally print invalid syntax into the file.
bool DebugPrintInvalidSyntax = false;