This breaks my code since my code detects __cpp_lib_ranges >= 201911L
I have checked cppreference, libstdc++, msvc stl, they all define __cpp_lib_ranges as 201911L. Clearly this is a bug.
Test runs successfully locally
Differential D111773
[libcxx] __cpp_lib_ranges value should be 201911L under C++20, not 201811L ldionne on Oct 13 2021, 8:07 PM. Authored by
Details
This breaks my code since my code detects __cpp_lib_ranges >= 201911L I have checked cppreference, libstdc++, msvc stl, they all define __cpp_lib_ranges as 201911L. Clearly this is a bug. Test runs successfully locally
Diff Detail Event Timeline
Comment Actions @expnkx please don't remove libc++ group for libc++ patches and please don't self approve.
Comment Actions [Github PR transition cleanup] This isn't relevant anymore since we now have: { "name": "__cpp_lib_ranges", "values": {"c++20": 202207}, "headers": ["algorithm", "functional", "iterator", "memory", "ranges"], }, Commandeering and closing. |
I think this change from 201811 to 201911 is correct. I'm willing to commandeer and land this 1-character-plus-autogenerated-files change. @ldionne, thoughts?
https://timsong-cpp.github.io/cppwp/n4861/version.syn#lib:__cpp_lib_ranges
However, notice the "unimplemented": True. That's correct as-is, because libc++ does not yet fully implement C++20 Ranges. We'll define the feature-test macro only once we have implemented the feature; that's what it's for!