Jordan Rose 9647483aee Warn when using '@_implementationOnly' inconsistently in a module (#24800) ...

I thought it would be useful to allow some uses of a module to be
'@_implementationOnly' and others to not be in case someone wanted to
change from one to the other gradually, but it turns out that if
you're trying to /make/ an import implementation-only, you want to
know everywhere you used it.

rdar://problem/50748157

2019-05-16 09:13:34 -07:00

..

exported-module-name-after

test: use #include rather than #import

2019-03-22 09:50:03 -07:00

exported-module-name-before

test: use #include rather than #import

2019-03-22 09:50:03 -07:00

imports-clang-modules

Add @_implementationOnly

2019-03-28 15:57:53 -07:00

imports-submodule-order

…

ConformancesUser.swift

Revert "[ParseableInterfaces] Skip value witnesses of resilient conformances" (#20637)

2018-11-16 11:21:14 -08:00

enums-layout-helper.swift

test: make portable to LLP64 targets (harder)

2019-05-06 08:32:34 -07:00

imports-other.swift

Warn when using '@_implementationOnly' inconsistently in a module (#24800)

2019-05-16 09:13:34 -07:00

make-unreadable.py

[windows] Fix handling of Network Service username.

2019-04-01 18:03:46 -07:00

opaque-result-types-client.swift

Opaque types require a newer Swift runtime.

2019-05-15 11:39:53 -07:00

other.swift

…

TestModule.swift

[ParseableInterface] Test that module-link-name is serialized and used

2018-11-27 18:06:28 -08:00