You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Existing Behavior and Potential Problems
Right now the compiler_id and built-in toolchain name for clang and msvc match, but for gcc they don't: The compiler_id is gnu while the built-in toolchain is called gcc. IMO this is confusing for no reason.
Describe Alternatives
Rename the compiler_id to gcc.
The text was updated successfully, but these errors were encountered:
I had not considered this discrepancy. Toolchains are probably going to see a significant refactor eventually. For now, I think the easiest and most compatible change is to accept both gcc and gnu for the compiler_id.
Existing Behavior and Potential Problems
Right now the
compiler_id
and built-in toolchain name forclang
andmsvc
match, but forgcc
they don't: Thecompiler_id
isgnu
while the built-in toolchain is calledgcc
. IMO this is confusing for no reason.Describe Alternatives
Rename the
compiler_id
togcc
.The text was updated successfully, but these errors were encountered: