-
Notifications
You must be signed in to change notification settings - Fork 576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generics not detected in framework code #191
Comments
Huh, this is strange, as it should be supported everywhere. |
Using pure Swift not Obj-C, so no @Class forwarding involved. |
Swift and objective-c generics are not compatible with each other, and so generic objective-c types are imported as normal types in swift (you can verify this by looking at |
In this case can you please open up the initial request for a Swift library for Bolts here: #61 And what's the team's plans on implementing this? Kind thanks. |
The rough answer is 'soon'. We do have eventual plans for it. But trying to come up with an API that allows easy swift & objc interop while maintaining the best feature compatibility between the two languages has proved difficult. |
Thanks for the update Richard. I imagine trying to reconcile both is going to be difficult indeed. Perhaps maintaining two separate API's, the exiting one and a clean-cut Swift-only API which also supports the new ErrorTypes conventions instead of NSError might be the way to go. |
I can't seem to get generics working in my framework project which pulls a dependency on Bolts.
The following error keeps coming up while compiling:
”Error:(17, 35) cannot specialize non-generic type 'BFTask'”
I've tried setting the iOS Deployment Target to iOS to ensure generics are supported in the minimum SDK level but still no luck. Any thoughts?
Note this seems to work just fine in the application project, it's only the framework project (which is a seperate .xcworkspace) that has this issue.
The text was updated successfully, but these errors were encountered: