# May we start using C++14 at the master branch?

**URL:** https://discourse.itk.org/t/may-we-start-using-c-14-at-the-master-branch/4172
**Category:** Engineering
**Created:** [May 31, 2021, 1:57pm UTC](https://discourse.itk.org/t/may-we-start-using-c-14-at-the-master-branch/4172 "2021-05-31T13:57:07Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Niels\_Dekker](https://discourse.itk.org/letter_avatar_proxy/v4/letter/n/9d8465/32.png) [@Niels\_Dekker](https://discourse.itk.org/u/Niels_Dekker)
#### Post date: [May 31, 2021, 4:36pm UTC](https://discourse.itk.org/t/may-we-start-using-c-14-at-the-master-branch/4172/3 "2021-05-31T16:36:35Z")

</div>

Thanks for your feedback @dzenanz We dropped Visual Studio 2013 more than three years ago already: [New Build Errors on CDash 1/24/18 - drop support for VS2013 in ITKv5?](https://discourse.itk.org/t/new-build-errors-on-cdash-1-24-18-drop-support-for-vs2013-in-itkv5/619)

So maybe it’s about time to drop VS2015 now. Especially because VS2017 and VS2019 have been around for quite a while now.

However, if it’s really necessary to keep supporting VS2015 for a while, it would still be great if we could already start using the C++14 subset that is implemented by VS2015. The most significant missing C++14 language feature would then be “Extended constexpr”, as I see at the link you added, [C++ compiler support - cppreference.com](https://en.cppreference.com/w/cpp/compiler_support#cpp14)

---

_[View the full topic](https://discourse.itk.org/t/may-we-start-using-c-14-at-the-master-branch/4172)._