Files
swift-mirror/test/Migrator/null_migration.swift
David Farler 63776b507b When converting some of the old Migrator automation to the new Migrator,
I had set up the driver to invoke a separate frontend invocation with
the "update code" mode. We sort of did this last release, except we
forked to the swift-update binary instead. This is causing problems with
testing in Xcode.

Instead, let's perform a single compile and add the remap file as an
additional output during normal compiles. The driver, seeing
-update-code, will add -emit-remap-file-path $PATH to the -c frontend
invocation.

rdar://problem/31857580
2017-04-27 01:03:00 -07:00

23 lines
475 B
Swift

// RUN: rm -rf %t && mkdir -p %t && %target-swift-frontend -c -update-code -primary-file %s -emit-migrated-file-path %t/migrated_null_migration.swift -emit-remap-file-path %t/null_migration.remap
// RUN: diff -u %s %t/migrated_null_migration.swift
// This file tests that, if all migration passes are no-op,
// there are no changes to the file.
protocol P {
func foo()
}
class C : P {
func foo() {}
}
struct S : P {
func foo() {}
}
enum E : P {
func foo() {}
}