Warn about the use of internal bridging headers without library evolution

It's very, very easy to make a mistake that will cause broken
serialized modules. Until that's no longer true, at least tell folks
that they are heading into uncharted waters, as we do with
`@_implementationOnly` imports.
This commit is contained in:
Doug Gregor
2025-09-19 16:19:17 -07:00
parent 903937a78f
commit b9f00ef923
3 changed files with 24 additions and 0 deletions

View File

@@ -609,6 +609,9 @@ ERROR(no_swift_sources_with_embedded,none,
ERROR(package_cmo_requires_library_evolution, none,
"Library evolution must be enabled for Package CMO", ())
WARNING(internal_bridging_header_without_library_evolution,none,
"using internal bridging headers without library evolution can cause instability", ())
ERROR(experimental_not_supported_in_production,none,
"experimental feature '%0' cannot be enabled in production compiler",
(StringRef))