> 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 pa

> 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.