Github user apocolipse commented on the issue:
https://github.com/apache/thrift/pull/1002
Yeah I think that would be the most appropriate way, making sure that
people that use it /want/ to use it and/or know that its not a Swift convention.
SPM integration should come with Swift 3.0 support, which while in beta now
is still not complete.
Sidenote: If anyone's interested I'm working on building a Pure-Swift
Thrift Library, basing it off of Swift 3.0 now (Started with Swift 2.0, but it
was limited to Mac/iOS environments due to Foundation use, now Swift Foundation
is part of Swift Standard Library 3.0 can be pushed for a public lib that works
on Linux + Mac) It's going to be in the works until Swift dev's finish up
Foundation (still a bit incomplete as of writing this) but it will be much more
"Swifty" (Following Swift 3.0 API Guidelines quite strictly), and may require
an updated Code generator as well. I'm not too familiar with the Code
generators so should someone like to work with me for a Swift 3.0 Library +
Code Generator that'd be great :D (Ideally i'm shooting to make it still
compatible with the existing Swift generator, but should any changes be needed
we should add a 3.0 generator option)
---
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.
---
