Lattner directly addresses this in a FAQ in the repository[1]
&quot;Do you plan to rewrite the Swift compiler in Swift?<p>Not in the short term. C++ is a very pragmatic language for implementing compilers, since it has good performance characteristics and allows higher-level programming idioms than C.<p>That said, we do expect Swift to a better language than C++ in a number of ways, so why don&#x27;t we implement the compiler itself in Swift? There are a couple of reasons that bootstrapping is not a good idea, at least in the short term:<p>This complicates bringup of the compiler, because you have to move both the compiled language and the compiler at the same time as the language evolves.
We want the language evolution and direction to be driven by general purpose programming challenges, not by the specific needs of compiler hackers. The urge to &quot;scratch our own itch&quot; might be too great.
That said, we are writing the runtime library in Swift itself. We may also decide to rewrite the compiler in Swift sometime in the distant future when the language settles down. At that point, it may be a good opportunity to revisit previous (internal to the compiler) design decisions, and we do expect and hope Swift to be a great language for doing many things, including implementing compilers.&quot;<p>1. <a href="https:&#x2F;&#x2F;github.com&#x2F;apple&#x2F;swift&#x2F;blob&#x2F;master&#x2F;www&#x2F;FAQ.rst" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;apple&#x2F;swift&#x2F;blob&#x2F;master&#x2F;www&#x2F;FAQ.rst</a>