4 ms·

Swift is a LLVM front-end just like Rust.

• hombre_fatal 7y ago
  You are saying that like it must then be as fast as Rust by this virtue.
  • zerr 7y ago
    No, semantics and idiomatic code matters but I don't think performance oriented Swift code would be significantly slower than Rust. I might be wrong though - feel free to share relevant benchmarks.
    • nicklauri 7y ago
      There are some benchmarks that I think you should give them a look: https://github.com/ixy-languages/ixy-languages https://github.com/ixy-languages/ixy-languages https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/swift-rust.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
      • zerr 7y ago
        Interesting, thanks! Ref counting has an overhead, of course. I wonder about the performance of the "performance oriented Swift code" - i.e. it would be non-idiomatic, but to avoid ref-counting - something you would write in your inner loop or other similar hot points.
        • nicklauri 7y ago
          Yes, they're programs from the benchmarks game that use a lot of UnsafeMutablePointer, which is: > provides no automated memory management or alignment guarantees. You are responsible for handling the life cycle of any memory you work with through unsafe pointers to avoid leaks or undefined behavior. [1] So I think they're "performance oriented Swift code". I'm not familiar with Swift, so sorry if I'm wrong. [1]: https://developer.apple.com/documentation/swift/unsafemutablepointer https://developer.apple.com/documentation/swift/unsafemutabl...
• fooker 7y ago
  That doesn't magically make Swift and Rust equally performant.