erichkeane wrote: @yashssh : We can take this offline (see slack), but Feature Test Macros are intended to change. The values listed in the standard are the 'minimum' value for a compiler that implemented every feature in the standard.
The expectation is that an implementation will use a number greater than that when implementing/enabling features from future standards. Since Clang is permitting this version of `static_assert` as an extension, it should be expected that the FTM is a value that would match. In this case, the Perennial test has an incorrect assumption, and, comparing a FTM with an equality comparison is actually contrary to how it is intended to be used(it should be `>=`, since the point is, "did you implement this one component of this feature that I want, or better?"). https://github.com/llvm/llvm-project/pull/102044 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
