Jordan Rose 2397bf4489 Under -enable-library-evolution, imports need Library Evolution too (#25549) ...

Otherwise, there's no guarantee of binary compatibility, and whoever
turned on library evolution support shouldn't be lulled into a false
sense of security.

This is just a warning for now, but will be promoted to an error later
once clients have shaken out any places where they're doing this.
Note that the still-experimental '@_implementationOnly' opts out of
this check, because that enforces that the import doesn't make its way
into the current module's public source or binary interface.

rdar://50261171

2019-06-18 09:22:56 -07:00

51 KiB

Raw Blame History

View Raw