search for: canonicalizationa

...of the other. I.e. you >> can't have two canonicalizations that "fight" each other. Using an explicit >> mutation API like the strawman above is a bit less bulletproof than >> scheduling based on statically known interferences between >> canonicalizations (e.g. CanonicalizationA may invalidate CanonicalizationB, >> but not the reverse, so it would automatically know to run >> CanonicalizationA before CanonicalizationB), but given that we have >> relatively few "canonicalizations" (to give them a name) that use this >> feature of the old PM...

...t have a subset of the requirements of the other. I.e. you can't have two canonicalizations that "fight" each other. Using an explicit mutation API like the strawman above is a bit less bulletproof than scheduling based on statically known interferences between canonicalizations (e.g. CanonicalizationA may invalidate CanonicalizationB, but not the reverse, so it would automatically know to run CanonicalizationA before CanonicalizationB), but given that we have relatively few "canonicalizations" (to give them a name) that use this feature of the old PM, it may be livable (at least in the...

The more closely I look at this, the more it seems like there may be a useful incremental step in the transition to the new PM: use the new PM analysis machinery in the old PM. If this is possible, it will simplify the old PM and (hopefully) allow an incremental transition to the new PM instead of a flag day transition for the switch. I.e., AFAICT, the new PM transition is essentially about 2