If anyone think it should re-write to a swift version, please leave a comment in this issue.

[bestwnh]

If anyone think it should re-write to a swift version, please leave a comment to tell me.
If this implement in swift, there are two plan:

1. Just a swift version, no api or struct change, will work fine in your project to replace the objective-c version.
2. A total new swift version with struct re-write and api change, can implement most of(not all) the old functions and some new effect. But maybe more change for replace the objective-c version.

Which one you prefer?

[cougarwww]

A swift version is wonderful

[akatasonov]

I'd like option 1 or 2. Doesn't matter much for me as long as it is Swift vs Objective-C.

[mjhassan]

Any option will do as long as it works with Swift3. Although, re-write will be great for both performance and memory. But if that cost you more time please stick to option 1.

[bestwnh]

@mjhassan you mean it won't work with Swift3 now?

[mjhassan]

I don't see any Swift3 branch, tag, badge or not even a mention in README.md. So I assumed it may not gonna support Swift3. Now after seeing your comment I created a dummy project and integrated and it works. +1 kudos.