mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
da07ff577c
PrintAsClang is supposed to emit declarations in the same order regardless of the compiler’s internal state, but we have repeatedly found that our current criteria are inadequate, resulting in non-functionality-affecting changes to generated header content. Add a diagnostic that’s emitted when this happens soliciting a bug report. Since there *should* be no cases where the compiler fails to order declarations, this diagnostic is never actually emitted. Instead, we test this change by enabling `-verify` on nearly all PrintAsClang tests to make sure they are unaffected. This did demonstrate a missing criterion that only mattered in C++ mode: extensions that varied only in their generic signature were not sorted stably. Add a sort criterion for this.
23 lines
658 B
Swift
23 lines
658 B
Swift
// RUN: %empty-directory(%t)
|
|
// RUN: %target-swift-frontend(mock-sdk: %clang-importer-sdk) %s -typecheck -verify -emit-objc-header-path %t/out.h
|
|
// RUN: %FileCheck %s < %t/out.h
|
|
|
|
// REQUIRES: objc_interop
|
|
|
|
import Foundation
|
|
|
|
// CHECK-LABEL: @interface PublicClass : NSObject{{$}}
|
|
public class PublicClass: NSObject {
|
|
// CHECK-NEXT: - (void)spiMember;
|
|
@_spi(A) @objc public func spiMember() {}
|
|
// CHECK-NEXT: init
|
|
} // CHECK-NEXT: @end
|
|
|
|
// CHECK-LABEL: @interface SPIClass : NSObject{{$}}
|
|
@_spi(B)
|
|
public class SPIClass: NSObject {
|
|
// CHECK-NEXT: - (void)publicMember;
|
|
@objc public func publicMember() {}
|
|
// CHECK-NEXT: init
|
|
} // CHECK-NEXT: @end
|