This workaround was already disabled for MSVC, as it resulted in a warning there, but it also gives a similar warning with clang and it seems better to restrict this workaround to gcc only rather than excluding another compiler.
This workaround was already disabled for MSVC, as it resulted in a warning there, but it also gives a similar warning with clang and it seems better to restrict this workaround to gcc only rather than excluding another compiler.