-
Notifications
You must be signed in to change notification settings - Fork 465
Make miri easier to install #520
Copy link
Copy link
Closed
Labels
A-uxArea: This affects the general user experienceArea: This affects the general user experienceC-enhancementCategory: a PR with an enhancement or an issue tracking an accepted enhancementCategory: a PR with an enhancement or an issue tracking an accepted enhancement
Metadata
Metadata
Assignees
Labels
A-uxArea: This affects the general user experienceArea: This affects the general user experienceC-enhancementCategory: a PR with an enhancement or an issue tracking an accepted enhancementCategory: a PR with an enhancement or an issue tracking an accepted enhancement
Type
Fields
Give feedbackNo fields configured for issues without a type.
It would be great if we could make miri easier to install.
miri + cargo miri
One thing is getting miri (and cargo-miri) itself. The ideal solution here would be making this a
componentin rustup so that it comes with a matching nightly. The dev-tools team has said they would support us in getting that done, after the edition.libstd
However, miri isn't extremely useful if libstd comes without all the MIR. Right now, I don't think just making it a component is going to do much good, if people still have to then clone our repo to run
xargo/build.sh.The best I can think of here is to do this automatically in miri itself: Basically, to move
xargo/*into the miri library, and have a setup step in the beginning which automatically compiles and then uses an appropriate libstd. Sounds rather hacky, but does anyone have a better idea?