Github user mfrawley commented on the issue:
https://github.com/apache/thrift/pull/1002
@apocolipse Like the ideas. Protocols can't be nested under a struct. You
get:
```
error: declaration is only valid at file scope protocol MyService {}
```
I like the Swift packages suggestion (which unfortunately are not in a
stable Swift release yet). Frameworks influence app startup time and
Cocoapods/Carthage already provide this functionality with podspecs (we use
Cocoapods atm).
A bigger issue we've run into when updating (since we generate code for
6+ client langs) is that we have property naming collisions .e.g. .code in
subtypes of NSError had to be renamed to errorCode, or .description. Being able
to have some way of dealing with that would be nice. One possible solution
might be a language-specific alias e.g. generate 'errorCode' for Swift, but
leave it as 'code' for other langs. That would avoid having to uglify all
client code with manually prefixed names. It's a different issue I know but
it's also name-collision related, and has cost me some considerable effort.
---
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.
---
