Files
swift-mirror/test/Macros/serialize_plugin_search_paths.swift
Daniel Rodríguez Troitiño ba68faaed5 [test] Mark tests that use experimental/upcoming features as such
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.
2024-11-02 11:46:46 -07:00

23 lines
994 B
Swift

// RUN: %empty-directory(%t)
// RUN: %target-build-swift %s -g -o %t/a.out \
// RUN: -emit-executable -emit-module \
// RUN: -Xfrontend -serialize-debugging-options \
// RUN: -module-name MyApp \
// RUN: -swift-version 5 -enable-experimental-feature Macros \
// RUN: -plugin-path %t/plugins \
// RUN: -external-plugin-path %t/plugins#%swift-plugin-server \
// RUN: -load-plugin-library %t/%target-library-name(MacroDefinition) \
// RUN: -load-plugin-executable %t/mock-plugin#TestPlugin
// RUN: %lldb-moduleimport-test -verbose -dump-module %t/a.out | %FileCheck %s
// REQUIRES: swift_feature_Macros
// CHECK: - Plugin Search Options:
// CHECK: -plugin-path {{.*}}plugins
// CHECK: -external-plugin-path {{.*}}plugins#{{.*}}swift-plugin-server
// CHECK: -load-plugin-library {{.*}}MacroDefinition.{{dylib|so|dll}}
// CHECK: -load-plugin-executable {{.*}}mock-plugin#TestPlugin
// CHECK-SYSV:-plugin-path {{.*}}plugins
// CHECK-SYSV:-plugin-path {{.*}}plugins