Harlan Haskins
f4b0e0e7b6
[Diagnostics] Mark invalid ‘@testable import’ as fatal
...
If this isn’t fatal, this will just end up cascading to a bunch of “could not find member … in …” errors, which hides the real issue.
2019-01-29 14:52:40 -08:00
Dmitri Gribenko
486cab447d
tests: replace 'rm -rf %t && mkdir -p %t' with '%empty-directory(%t)'
...
These changes were made using a script.
2017-06-04 11:08:39 -07:00
David Farler
b7d17b25ba
Rename -parse flag to -typecheck
...
A parse-only option is needed for parse performance tracking and the
current option also includes semantic analysis.
2016-11-28 10:50:55 -08:00
Dmitri Gribenko
55864d10cb
Tests: use 'mkdir -p'
2016-09-02 21:36:45 -07:00
Chris Lattner
fc64acb4ae
Add fixit checks to various test/attr tests.
...
Swift SVN r31002
2015-08-04 20:29:00 +00:00
Jordan Rose
8ad5297001
Don't complain when using '@testable import' on a Clang-only module.
...
Justification: if you delete all the Swift code out of a framework,
you shouldn't have to change your tests.
rdar://problem/21207346
Swift SVN r29452
2015-06-17 17:52:44 +00:00
Jordan Rose
8a3fcf621e
Add -disable-testable-attr-requires-testable-module.
...
...which allows "@testable import" to work with modules not compiled for
testing. This isn't generally safe, but should be fine for clients like
SourceKit which just need to have the API available and might not be able
to properly rebuild the original target for testing.
We may revisit this in the future.
Swift SVN r26629
2015-03-27 16:36:41 +00:00
Jordan Rose
e6c2131bda
Check that "@testable import Foo" is only used to import testable modules.
...
(i.e. modules compiled with -enable-testing)
Part of testability (rdar://problem/17732115)
Swift SVN r26293
2015-03-19 02:20:41 +00:00
