cfg_select! looks good. cfg_if! always added so much boilerplate that it rarely reduced complexity, even though it offered a valid solution for when you had a complex condition in one branch and then not() that in the other. It was also annoying that you had to add a dependency for those rare cases.
We did also move away from cfg_if!, though, because IDE tooling would mostly just quit working within the cfg_if! macro call. Will have to see, if that’s better with this compiler built-in, or if the IDE tooling gets updated to support that well.
cfg_select!looks good.cfg_if!always added so much boilerplate that it rarely reduced complexity, even though it offered a valid solution for when you had a complex condition in one branch and thennot()that in the other. It was also annoying that you had to add a dependency for those rare cases.We did also move away from
cfg_if!, though, because IDE tooling would mostly just quit working within thecfg_if!macro call. Will have to see, if that’s better with this compiler built-in, or if the IDE tooling gets updated to support that well.