> > If we're re-writing C devices in Rust, we need to be able to promptly > > drop the C impl once the Rust impl is feature complete. Keeping 2 impls > > is a general maint burden, as well as an ongoing vmstate compatibility > > danger if a change in one impl is not matched by an identical change > > in the other impl. > > I agree. One more reason why "Let's Rewrite It In Rust" is more of a > necessary evil to bootstrap the creation of bindings, and not a good > idea in general.
Hi Paolo and Daniel, about this point, what things can be done to help the community move towards dropping duplicate impl? For example, about HPET, add test cases (similar to tests/qtest/m48t59-test.c) to check register read/write to prove that the two impls are consistent? Thanks, Zhao
