Hello everyone, I also came from the tweet that oli made, so if there's something to gets my hands dirty I'm down!
@choco I have something that isn't actually an optimization, but validates that our optimizations don't generate broken code. The work for this is exactly the same as one does for optimizations, so I think it's a good starter. https://github.com/rust-lang/rust/issues/73832
I wrote some quickstart instructions in https://rust-lang.zulipchat.com/#narrow/stream/189540-t-compiler.2Fwg-mir-opt/topic/multiple.20return.20terminators/near/203699347
the part of creating a test does not apply to you, you just rerun the command after your changes
Is libcore building with validation? I thought it was broken.
oh... maybe then that's not a good issue to start with
Ok, different thing. I have something: https://github.com/rust-lang/rust/issues/65693 . If you want to take that issue, you'd be optimizing the MIR datastructures, making MIR optimizations less complex, instead of optimizing instances of MIR.
Again, no custom issue is requires, and no change in test output expected
I'm gonna throw some more documentation on that issue
let me know if you run into any situations that require non-trivial code changes
Thanks! I will start looking at this today after work :)