[hypeatei]

Yes, here[0]. Although, it's not anywhere close to being used for everyday things. There are blockers listed in their GitHub issues and various issues posted to the Swift forums.

[0]: https://xcancel.com/awesomekling/status/1822236888188498031

[abnercoimbre]

Thank you! I'd imagine performance-sensitive components in the engine need to remain in C++ (or a similar systems language) right? However, I'm not privy to Swift's runtime benchmarks.

[karulont]

Swift has been adding support for things like non-copyable types that should help with writing performance sensitive parts.

[hypeatei]

> imagine performance-sensitive components in the engine need to remain in C++

I'd imagine so, yes. I think the vision is to use Swift in "risky" areas like parsing data for example. Probably much more too, but the big hitters would be safety critical areas I think.