Skip to content
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

Cocoapods support #80

Open
piercifani opened this issue Mar 14, 2018 · 3 comments
Open

Cocoapods support #80

piercifani opened this issue Mar 14, 2018 · 3 comments

Comments

@piercifani
Copy link

I've found this library to be quite useful for development on iOS projects.

Would you mind if I created a podspec with this so it can be used from iOS projects?

@0xTim
Copy link
Member

0xTim commented Mar 14, 2018

@piercifani that library is about to be gutted if not completely removed with the introduction of Swift NIO...

You are probably better off forking it and adding a podspec to that!

@piercifani
Copy link
Author

But even if Swift NIO declares its own Future, would every module on vapor that needs a Future be required to import NIO?

@0xTim
Copy link
Member

0xTim commented Mar 15, 2018

So I haven't looked into the NIO integration too much but I believe that Vapor/Vapor will wrap the NIO types into the something that look familiar (could be completely wrong). At worst Vapor can just @_export NIO to expose all of the types without the need for another import

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants