I'm very interested in finding out what people's opinions are on approaches to resolving https://github.com/rust-lang/miri/issues/196
The most naive approach (and most labour intensive) would be to build a dedicated MIR front-end right?
Would that ever be worthwhile?
I mean that would be pretty sweet
That would also probably help us testing the soundness of the MIR-opt transforms
I suspect that we might end up with something like that as part of the Sealed Rust effort, but probably only in a couple of years
Like no-source libraries?
I think it could be useful for negative testing of MIR-optimizations
Like "given this weird MIR that's really difficult to generate from Rust, the optimization doesn't do the wrong thing"
But it doesn't seem a huge priority to me
Thinking about it, it would be something that should be fairly easy to build incrementally
And could be done as part of the ramp up for Sealed Rust?
Yeah, I think there are uses for it and some people would certainly like to have it, but I don't know it's something the compiler team would focus on in the next year or so
That's my personal opinion
yea, you could totally start out with just a parser extension that adds
mir foo(x: type) -> ret_type syntax and incrementally add features step by step. The easiest way to gauge whether it's worthwile to pursue without putting a lot of work into it is to write an MCP to the compiler team with a plan for how to do this
Ok I'll give that a go! Thanks Oli!