Here is a tracking issue for all the steps I can think of, before we need to start going through all the various runtime logic, and actually use the new multi-dimensional weights v2.
Once we get to that point, we will need to double check our logic around benchmarking and PoV, and we can open a new tracking issue for that.
Here is a tracking issue for all the steps I can think of, before we need to start going through all the various runtime logic, and actually use the new multi-dimensional weights v2.
RefTimeWeightRemove RefTimeWeight substrate#12157Ordfrom the one dimensional weight type Remove Ord impl for Weights V2 and add comparison fns substrate#12183any_gtany_ltall_gtall_lt(and the equal to variant)any_*orall_*. This is super important, because it could lead to bugs if incorrectly implemented, and we have 2 dimensional weights.sp-weightsCreate sp-weights crate to store weight primitives substrate#12219#[compact], and include that in the migration: Make new Weight struct#[codec(compact)]substrate#12149benchmark overheadRecord PoV size inbenchmark overhead#384Once we get to that point, we will need to double check our logic around benchmarking and PoV, and we can open a new tracking issue for that.