mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
ba68faaed5
Find all the usages of `--enable-experimental-feature` or `--enable-upcoming-feature` in the tests and replace some of the `REQUIRES: asserts` to use `REQUIRES: swift-feature-Foo` instead, which should correctly apply to depending on the asserts/noasserts mode of the toolchain for each feature. Remove some comments that talked about enabling asserts since they don't apply anymore (but I might had miss some). All this was done with an automated script, so some formatting weirdness might happen, but I hope I fixed most of those. There might be some tests that were `REQUIRES: asserts` that might run in `noasserts` toolchains now. This will normally be because their feature went from experimental to upcoming/base and the tests were not updated.
16 lines
643 B
Swift
16 lines
643 B
Swift
// This test verifies that command line parsing restricts use of features that
|
|
// are not allowed non-production compilers.
|
|
|
|
// REQUIRES: no_asserts
|
|
// REQUIRES: swift_feature_AccessLevelOnImport
|
|
|
|
// 'AccessLevelOnImport' is allowed in production
|
|
// RUN: %target-swift-frontend -typecheck %s -enable-experimental-feature AccessLevelOnImport -verify
|
|
|
|
// 'ParserValidation' is NOT allowed in production
|
|
// RUN: not %target-swift-frontend -typecheck %s -enable-experimental-feature ParserValidation 2>&1 | %FileCheck %s
|
|
|
|
// CHECK: <unknown>:0: error: experimental feature 'ParserValidation' cannot be enabled in production compiler
|
|
|
|
import Swift
|