Umbrella Foundation import appears despite Foundation being only imported qualified
| Originator: | widmannrobert | ||
| Number: | rdar://20867951 | Date Originated: | 07-May-2015 08:54 PM |
| Status: | Open | Resolved: | |
| Product: | Developer Tools | Product Version: | Xcode 6.4 (6E14) |
| Classification: | Serious Bug | Reproducible: | Always |
Summary: When creating a Swift framework for either iOS or OS X and using only qualified imports for Foundation, the resulting generated header for said framework still contains a global import of foundation and all its symbols because sub-parts of Foundation themselves import globally. Steps to Reproduce: 1. Use Xcode's Framework template for Mac or iOS to create a new framework. 2. Qualified import any foundation Foundation class. 3. Create a new project. 4. Link with the framework that was just created and import it into a file. 5. CMD+Click the import to jump to the autogenerated header. Expected Results: Only the qualified part of Foundation appears in the imports section of the auto-generated header. Actual Results: All of Foundation appears imported unqualified in the auto-generated header. Version: Xcode 6.4 (6E14) Notes: Configuration: Attachments:
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!