Operand::Movedo you think it would be error-prone to have
Operand::Copy be one
Operand::Consume again and adding a second field for differentiating?
so, how do you like an
Operand::consume method returning an
for all the code that matches on
anything that doesn't care is likely visiting through operands anyway
there's loads of duplication
well... unfortunately the "likely" is not true. We have quite a few of such matches
I guess it depends on the kind of code. but I would expect at least some of them to start treating copies and moves differently
just grep for
Operand::Copy in https://github.com/rust-lang/rust/pull/60913/files
sigh why am I not pinged on that PR?
because it's nowhere ready
we're using it as a canary for smaller PRs
yeah but I'd like to know when each of those PRs goes up :P
to hype myself up about them if nothing else!