mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
e4cf74abfa
For the most part, the differences between the diagnostics introduced
by the C++ implementation and the new SwiftIfConfig implementation are
cosmetic, so these are only wording changes.
The one major difference is that we've dropped the warnings about
potential typos in os/arch checks. For example, if one writes:
#if os(bisionos)
// ...
#endif
The C++ implementation will produce a warning "unknown operating system
for build configuration 'os'" with a note asking "did you mean
'visionOS'"? These warnings rely on a static list of known operating
systems and architectures, which is somewhat unfortunate: the whole
point of these checks is that the Swift you're dealing with might not
have support for those operating systems/architectures, so while these
warnings can be helpful in a few cases, they also cause false
positives when porting. Therefore, I chose not to bring them forward.
29 lines
799 B
Swift
29 lines
799 B
Swift
// RUN: %target-typecheck-verify-swift
|
|
|
|
// expected-error@+1{{invalid conditional compilation expression}}
|
|
#if hasGreeble(blah)
|
|
#endif
|
|
|
|
// Future compiler, short-circuit right-hand side
|
|
#if compiler(>=10.0) && hasGreeble(blah)
|
|
#endif
|
|
|
|
// Current compiler, short-circuit right-hand side
|
|
#if compiler(<10.0) || hasGreeble(blah)
|
|
#endif
|
|
|
|
// This compiler, don't short-circuit.
|
|
// expected-error@+1{{invalid conditional compilation expression}}
|
|
#if compiler(>=5.7) && hasGreeble(blah)
|
|
#endif
|
|
|
|
// This compiler, don't short-circuit.
|
|
// expected-error@+1{{invalid conditional compilation expression}}
|
|
#if compiler(<5.8) || hasGreeble(blah)
|
|
#endif
|
|
|
|
// Not a "version" check, so don't short-circuit.
|
|
// expected-error@+1{{invalid conditional compilation expression}}
|
|
#if os(macOS) && hasGreeble(blah)
|
|
#endif
|