Github user creker commented on the pull request:
https://github.com/apache/thrift/pull/539#issuecomment-147547155
From the code it difficult to see what's the problem. Yes, in objc
selectors are separate from the classes - they're shared between them and
stored as plain strings. That creates problems only when you're dealing with
`id` objects - compiler doesn't have type information. When you call method on
`id` compiler will search for any class that contains the selector. But if your
variable have a specific type then compiler will know what to do. Even with
`id` I don't remember any conflicts - compiler just silently lets me call any
selector that it can find which may crash at runtime because that particular
object doesn't implement it.
---
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.
---
