> On 22 Jul 2020, at 17:30, Thiago Macieira <thiago.macie...@intel.com> wrote: > > On Wednesday, 22 July 2020 03:24:30 PDT Lars Knoll wrote: >> no_unique_address is coming and making that problem go away. It’s available >> on all compilers except MSVC today (see >> https://en.cppreference.com/w/cpp/compiler_support#cpp2a). >> >> We want things to work on C++17 and that’s what we have. But we can and >> should plan for C++20. > > Please reconfirm you are willing to: > > a) require GCC 9.0 and Clang 9.0 > b) not use [[no_unique_address]] in MSVC and clang-cl until Qt 7 > c) drop support for any other compilers until they support > [[no_unique_address]] > > (I think we only have two other supported compilers: Green Hills' and Intel's)
I still don’t understand why you think this should be necessary. All we need to do is clearly document that enabling/disabling the support for this feature is not binary compatible and make sure users don’t mix by accident. Cheers, Lars > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel DPG Cloud Engineering > > > > _______________________________________________ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
