Is there a way to get #Apple #Clang to warn on aggregate initialization w/ designated initializers in the wrong order? In C++ it's supposed to be illegal to aggregate-initialize a struct in any other order than declaration order, but Clang never warns on that so I don't catch it until CI complains or I try to compile the code on a Linux machine

#LLVM #appleclang

Ugh. It's irritating that certain C++20 features still aren't in the most current #AppleClang :
- std::ranges
- `<=>`
- std::jthread and std::stop_token
- std::source_location

Especially for cases where one simply can't just use regular #Clang .

Check out the current support status across the board: https://en.cppreference.com/w/cpp/compiler_support/20

#cpp #cpp20 #ranges #spaceshipoperator