mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
517f5d6b6a
Way back in Swift 1 I was trying to draw a distinction between "overlays", separate libraries that added Swift content to an existing Objective-C framework, and "the Swift part of a mixed-source framework", even though they're implemented in almost exactly the same way. "Adapter module" was the term that covered both of those. In practice, however, no one knew what "adapter" meant. Bring an end to this confusion by just using "overlay" within the compiler even for the mixed-source framework case. No intended functionality change.
9 lines
564 B
Swift
9 lines
564 B
Swift
// RUN: %empty-directory(%t)
|
|
|
|
// RUN: %target-swift-frontend -emit-module -parse-as-library %S/Inputs/overlay.swift -sdk %S/Inputs -I %S/Inputs/custom-modules -module-name ClangModuleWithOverlay -o %t
|
|
// RUN: %target-swift-frontend %s -sdk %S/Inputs -I %S/Inputs/custom-modules -I %t -typecheck
|
|
// RUN: %target-swift-frontend %s -I %t -typecheck -show-diagnostics-after-fatal -verify
|
|
|
|
// When run without the underlying SDK, we should get an error here.
|
|
import ClangModuleWithOverlay // expected-error{{cannot load underlying module for 'ClangModuleWithOverlay'}}
|