[SR-11918] Reject the combination of -enable-testing and -enable-library-evolution #54337
Labels
compiler
The Swift compiler itself
diagnostics QoI
Bug: Diagnostics Quality of Implementation
good first issue
Good for newcomers
improvement
legacy driver
Area → compiler: the integrated C++ legacy driver. Succeeded by the swift-driver project
Additional Detail from JIRA
md5: ab250be10d119aca78692308209cbd17
Issue Description:
We know that testability and library evolution have serious compatibility issues. In particular,
@testable import
of modules with library evolution can cause the compiler to inline code that was optimized with one resilience expansion into a context that requires a different resilience expansion. Rather than waiting for users to encounter bizarre compiler or even runtime crashes when building tests, we should emit a warning or error when the library itself is compiled with both-enable-testing
and-enable-library-evolution
.The text was updated successfully, but these errors were encountered: