binds

❤️🦀❤️ rust for life

> For the record, on nightly, both `import` and `using` suggest using `use`. I'm sure it's not that difficult to add `require`. ah. I was not aware of this. Less...

> @gimbles And also add `include`? Rust may go tooooo friendly in diagnostic message 😊. Do you mind that I make a PR for it? I'm a newbie in hacking...

@rustbot claim

@RalfJung as you directed me in the referenced issue, here is the output, at the point when it fails, of `cargo miri setup -v --target CUSTOM_TARGET` when I run it:...

> Is that the full output? It doesn't contain the extra infoemation that "-v" would print. > > Also I was asking about "cargo miri setup -v" without "--target". I...

``` Preparing a sysroot for Miri (target: x86_64-unknown-linux-gnu)... Compiling compiler_builtins v0.1.85 Compiling core v0.0.0 (/home/binds/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core) Compiling libc v0.2.138 Compiling cc v1.0.77 Compiling memchr v2.5.0 Compiling std v0.0.0 (/home/binds/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std) Running `/home/binds/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/cargo-miri...

> It looks like cargo does both a regular build as well as a check build of several crates for some reason. Do you have build-std in .cargo/config.toml or something?...

I came across this issue again while looking through the issue list. I would be interested in contributing a fix for this as it would be beneficial for me, and...

> the rest heavily depends on how exactly -Zbuild-std works inside cargo. So this could end up requiring a bunch of exploration and debugging the complicated flow of control between...