eonil
Then it seems to be a bug in C API layer.
This is related to issue #1. I still couldn't find a good way to determine whether the type has been correctly resolved or not, but missing types can be resolved...
I still couldn't find a good way to determine whether the type is resolved or just implicitly assumed to `int`. Anyway, you will get `diagnostic`s if something goes wrong, so...
RIP Alex.
This also happens with `Apple Swift version 3.1 (swiftlang-802.0.53 clang-802.0.42)` on Sierra `10.12.5 (16F73)`.
+1 for this. Please consider providing an official type definitions. Type annotation and checking is essential for productivity to me. Supporting TypeScript does not harm any existing JavaScript users.
Writing to a file in an app bundle doesn't seem to be a good practice.
Hello @amine2233 , sorry for late reply. I can't reproduce your issue on my local machine. Can you explain me some more details? Like actual directory file structure? 4 seconds...
+1 for this. Type annotation & check is the key for productivity. Please consider.
Hello @Cee. I don't have support for CocoaPods now. Maybe later, but I can't promise a specific date. I can't make much time for this project nowadays. Of course, pull-request...