为何SnapKit仅需导入一次即可全局使用，SwiftyJSON需逐文件导入？

Great question! I’ve stumbled on this exact discrepancy myself while working with CocoaPods and Swift libraries, so I totally get the confusion. Let’s break down what’s going on here, using your examples of SnapKit and SwiftyJSON.

Why SnapKit works everywhere after one import #

There are two common reasons for this behavior:

• You used @_exported in a global scope file: If you added something like @_exported import SnapKit in a file accessible to your entire project (like AppDelegate.swift, a dedicated GlobalImports.swift, or your project’s main Swift entry file), this keyword makes all of SnapKit’s symbols available globally. Any other file in your project will automatically have access to SnapKit without needing to re-import it.
• Precompiled header or modular header configuration: If your project uses a precompiled header (.pch file) and you added #import <SnapKit/SnapKit.h> to it (for Objective-C compatibility), or you enabled use_modular_headers! in your Podfile, SnapKit’s interface gets exposed across the project. This is less common for pure Swift libraries like SnapKit, but it’s still a possible scenario.

Why SwiftyJSON needs per-file imports #

This boils down to standard Swift module behavior:

• No global export setup: Unlike SnapKit (in your case), you haven’t added @_exported import SwiftyJSON to any global scope file. By default, Swift modules are file-scoped—importing a module in one file only makes it available within that file. Every other file that wants to use SwiftyJSON has to explicitly import it with import SwiftyJSON.
• SwiftyJSON’s default podspec configuration: SwiftyJSON is packaged as a standard Swift module with no special global exposure settings in its podspec. It follows Swift’s default visibility rules, so explicit per-file imports are required unless you set up the global export yourself.

The Underlying Swift Module Import Rule #

At its core, Swift’s module system is designed to keep dependencies explicit by default. When you import a module without @_exported, it’s only visible to the current file. The @_exported keyword overrides this—it marks the imported module as a public dependency of your project’s main module, making its symbols accessible to every file in your project automatically.

Note: If you’re working in an Objective-C/Swift mixed project, importing an Objective-C library via the bridging header lets Swift files use it without explicit imports—but this doesn’t apply to pure Swift libraries like SnapKit and SwiftyJSON.

内容的提问来源于stack exchange，提问作者Hobson