🛠 Heavily guard existing FMT_OUTPUT_RANGES for terrible compilers
This commit is contained in:
parent
5982f05269
commit
ee799d6fdb
@ -144,7 +144,11 @@
|
||||
// Only on if we know we can do the begin/end range checking properly,
|
||||
// that we have `if constexpr`, and that we have a std::ranges::subrange type
|
||||
#ifndef FMT_OUTPUT_RANGES
|
||||
# if FMT_RANGE_CHECKS && defined(__cpp_if_constexpr) && defined( __cpp_lib_ranges)
|
||||
# if FMT_RANGE_CHECKS \
|
||||
&& defined(__cpp_if_constexpr) && (__cpp_if_constexpr >= 201606L)\
|
||||
&& defined(__cpp_lib_ranges) && (__cpp_lib_ranges >= 201911L )\
|
||||
&& defined(__cpp_concepts) && (__cpp_concepts >= 202002L) \
|
||||
&& defined(__cpp_lib_concepts) && (__cpp_lib_concepts >= 201907L)
|
||||
# define FMT_OUTPUT_RANGES 1
|
||||
# else
|
||||
# define FMT_OUTPUT_RANGES 0
|
||||
|
||||
Loading…
Reference in New Issue
Block a user