We do continue to work on the most considerable improvements, such as:
– Auto-detection between let and var declarations;
– Support for public vs private accessors depending on the scope;
– Using Apple SourceKit to precisely import Obj-C to Swift method mappings.
Any feedback or suggestions on what else should we prioritize are definitely welcome!
]]>With the big projects, might be bigger than rewrite, especially if you want to redesign architecture and patterns which is most bigger projects need after some time. Even then the tool is useful to convert simple files or snippets and you would just do final Swifty fixes.
Cheers
Michał
However, could you recommend this kind of tool for a full project conversion? If migration from Obj-C to Swift is done manually, the outcome is often much shorter, simpler and safer (also because moving the old Obj-C codebase to a newer version of the SDK). If there is no time for manual migration and improvements, probably there is also no time for checking the whole converted project for potential bugs which, in my opinion, can be very time consuming. Additionaly Swiftify is not a cheap solution.
On the other hand it seems to be the perfect tool for converting Obj-C snippets from the stack overflow and use them natively in our Swift project 🙂
]]>