MachineChoice is a mesonlib object, not a compilers object, so it makes no sense to import it from the latter simply because the latter imports it too. This results in brittle module dependencies and everything breaking when a refactor removes it from the latter. ... also it is a typing-only import so while we are fixing it to import from the right place, we can also put it in a type-checking block.pull/10489/head
parent
075ccc68be
commit
46148f923b
1 changed files with 3 additions and 1 deletions
Loading…
Reference in new issue