summaryrefslogtreecommitdiff
path: root/test/Modules/implicit-private-with-submodule.m
Commit message (Collapse)AuthorAgeFilesLines
* [Modules] Improve .Private fix-its to handle 'explicit' and 'framework'Bruno Cardoso Lopes2018-06-151-1/+10
| | | | | | | | | | When in the context of suggestion the fix-it from .Private to _Private for private modules, trim off the 'explicit' and add 'framework' when appropriate. rdar://problem/41030554 git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@334859 91177308-0d34-0410-b5e6-96231b3b80d8
* [Modules] Improve fixit for framework private module mapsBruno Cardoso Lopes2018-03-301-1/+1
| | | | | | | | | The wrong source range was being provided in some case, fix that to get a better fixit. rdar://problem/38520199 git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@328857 91177308-0d34-0410-b5e6-96231b3b80d8
* [Modules] Change private modules rules and warningsBruno Cardoso Lopes2017-12-221-0/+36
We used to advertise private modules to be declared as submodules (Foo.Private). This has proven to not scale well since private headers might carry several dependencies, introducing unwanted content into the main module and often causing dep cycles. Change the canonical way to name it to Foo_Private, forcing private modules as top level ones, and provide warnings under -Wprivate-module to suggest fixes for other private naming. Update documentation to reflect that. rdar://problem/31173501 git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@321337 91177308-0d34-0410-b5e6-96231b3b80d8