We first shipped the rejuvenation work with VS 2015, but we’re still working on it today. We call this work “compiler rejuvenation,” a term that’s used in Jim Springfield’s excellent blog post from September 2015. In 2015 we started on a project that would fundamentally change how our compiler parses and analyzes code. We also maintain an open source fork of the Ranges TS that works on our compiler. In addition to our participation in the standards committee meeting, editors from three major Technical Specifications (Coroutines, Modules, and Ranges) work on the MSVC team. The MSVC team is a major contributor to the development of the C++ Standard. We’re not just implementing the C++ Standard, we’re helping to develop it. This post will look back on the progress we’ve made in MSVC and look forward to our plans in the next version. Our team has been focused on making MSVC the best compiler toolset for your development on Windows, and that starts with fully conforming to the existing C++ Standard. Since we first shipped Visual Studio 2015 we’ve talked a lot about Microsoft Visual C++ compiler and library (MSVC) conformance improvements in this blog.
0 kommentar(er)
