3 ms·
1. Inferred static nominal typing with generics 2. 1st class support for Optionals 3. Support for Structs and Classes 4. Native binary & scripting mode 5. A
by supster 10y ago
1. Inferred static nominal typing with generics
2. 1st class support for Optionals
3. Support for Structs and Classes
4. Native binary & scripting mode
5. Automatic reference counting (instead of garbage collection)
6. Large standard library
7. Large corporate backer (Apple)
8. Open source
9. Good C, C++, & Obj-C interoperability
10. Decently fast (https://medium.com/@qutheory/server-side-swift-vs-the-other-guys-2-speed-ca65b2f79505#.1fj3tnmxa https://medium.com/@qutheory/server-side-swift-vs-the-other-...)
- stepanhruda 10y agoNon C++ interop yet
- supster 10y agoYou're right, I believe it's on the road map
- 0xCMP 10y agoBut good Objective-C interop for working with old app code and libraries (Which comes from the C support, but with all the special stuff done to talk to Obj-C done for you)
- pjmlp 10y agoNo, but one can make use of Objective-C++ as a way to create Swift wrappers.