Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Still on an Objective-C runtime, so it's hard to see how the performance gains they claim are achievable, but otherwise having an interpreted version should be good for productivity.


Correct me if i'm wrong, but Swift has static typing (with type inference, but still with a strict type on every variable), whereas Objective C has dynamic typing with optional type annotations. Having ubiquitous strong type information available should make it much easier to generate fast code.


Hm, maybe that's it. I thought typing was still dynamic because of the multiple return types.


guessing multiple return types are supported by just returning a tuple?


maybe it is accompanied by improvements in LLVM? Or optimizations in LLVM that are more feasible with Swift (it has immutable values).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: