@asb
Interesting. I assume it’s the “allocating” variety of embedded Swift you’re thinking of, ie classes still supported and there’s still a heap?
Is it the sheer download size of the type metadata necessary for erasure, existentials, etc that’s the barrier with current Swift?