After reading <a href="http:&#x2F;&#x2F;blogs.msdn.com&#x2F;b&#x2F;vcblog&#x2F;archive&#x2F;2015&#x2F;09&#x2F;25&#x2F;rejuvenating-the-microsoft-c-c-compiler.aspx" rel="nofollow">http:&#x2F;&#x2F;blogs.msdn.com&#x2F;b&#x2F;vcblog&#x2F;archive&#x2F;2015&#x2F;09&#x2F;25&#x2F;rejuvenati...</a> i&#x27;m not really surprised about these kind of issues. It&#x27;s impressive that VC2013 was as compliant as it was, when all template parsing was based on string interpolation instead of an AST (and simultaneously distressing that a billion-dollar company would release such a product so recently).<p>Is the submitted article talking about VC2015? Although i suppose they will need to keep supporting the older toolchains.