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.
18 lines
730 B
Swift
18 lines
730 B
Swift
// REQUIRES: swift_swift_parser
|
|
// REQUIRES: swift_feature_ParserValidation
|
|
|
|
// Checks that skipping function bodies doesn't cause the new parser validation
|
|
// to fail. This can currently be the case because the new parser doesn't
|
|
// support skipping, causing validation fail as it generates diagnostics when
|
|
// the C++ parser would not.
|
|
|
|
// RUN: %target-typecheck-verify-swift -enable-experimental-feature ParserValidation
|
|
// RUN: %target-swift-frontend -typecheck %s -enable-experimental-feature ParserValidation -experimental-skip-all-function-bodies
|
|
|
|
func bad() {
|
|
_ = [(Int) -> async throws Int]()
|
|
// expected-error@-1{{'throws' may only occur before '->'}}
|
|
// expected-error@-2{{'async' may only occur before '->'}}
|
|
}
|
|
|