https://bugs.kde.org/show_bug.cgi?id=453759
--- Comment #8 from Friedrich W. H. Kossebau <kosse...@kde.org> --- Nicolas: I am curious: given ksyntaxhighlighting itself is set to use C++17 during its build, does MSVC fail to react to that and still make C++20 headers visible or even use them? Or, when you say "Compile KSyntaxHighlighting with Visual Studio 2022 in C++20 mode" you mean, you modified the normal build and actually enforce C++20 instead? So anyone else should not be really affected for now? And in that case, why would you build with C++20 and not just the default C++17? Does that affect the output in any way? And should it perhaps be an option supported by upstream (in case this is also interesting for others)? -- You are receiving this mail because: You are watching all bug changes.
