Github user apocolipse commented on the issue:
https://github.com/apache/thrift/pull/1002
So for Cocoapods/Carthage, you're also using Frameworks (startup time is
negligible). I'd almost recommend manually handling separate Podspec's to keep
things Module scope namespaced, it doesn't seem right at this point to have
Thrift generate Carthage/Cocoapods configurations. SPM should be good enough
when Swift 3.0 is stable to where it can point to specific files for modules,
additionally Foundation is ready for server side use then as well so perhaps
SPM is the way to go.
Either way I wouldn't recommend this as a 1st-class feature for Swift code
generation from Thrift. Perhaps as an option "Use Obj-C Cocoa Namespacing", so
that its explicitly clear that this isn't a Swift convention, but an old
Obj-C/Cocoa convention.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
