Github user apocolipse commented on the issue:
https://github.com/apache/thrift/pull/1084
@nsuke I considered that when starting out, however the differences between
Swift 2 and 3 are pretty dramatic that makes shared code minimal (i.e.
everything in this library is Value typed, compared to the Swift/Cocoa
generator).
Conceptually, this /is/ the `Swift` generator, and the other one is
technically Cocoa Swift.
Additionally, due to limitations with SPM, sharing code might not be the
most sane option.
One key difference with this and the existing Swift library, this library
has no intention of Objective-C interop, it is a pure Swift approach.
We could argue for moving the old Swift generator to be used like `--gen
cocoa:swift` which would be more appropriate in my opinion.
As far as sharing code between them goes, the amount that is the same
should be negligable, but packaging is the biggest concern. Cocoapods isn't
overly friendly with picking/choosing source files from different locations in
the file heirarchy, and SPM isn't capable of pointing at sources not in
`Sources` at all (hence the need for a separate repo for the time being to
leverage it with SPM).
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
