Philipp Oppermann

I think it's more a convenience method than an inconsistency. It behaves as expected and has no influence at all on the RAII based API. So it's kind of similar...

I tried to find prior art for such a method and found https://github.com/rust-lang/rust/pull/61976, which proposed adding a similar method to the `Mutex` of the standard library. It was closed because...

Thanks for reporting! I'm happy to merge a PR for this.

`TryFrom` is on the verge to stabilization. It is already included in the current beta, which will become Rust 1.43 on the 11th April.

A naked extern function with `#[no_mangle]` should work. However, I'm not sure if inline assembly supports the `bits 32` directive, which we use to generate 32 bit opcodes in nasm...

We don't pass RUSTFLAGS when building `core` and the other sysroot crates because we need to set our own RUSTFLAGS. If your project works with cargo's `build-std` feature, I recommend...

This is not supported currently and I don't think that we will add a feature like this, given that this crate is likely replaced by the [`-Zbuild-std` feature](https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#build-std) of cargo...

That's strange. Do you have your code somewhere online so that I can test myself?

Thanks! I'm able to reproduce it. cc @lachlansneff I think this is the same error as you had with the new version of raw_cpuid.

That's really strange. Without the build dependencies it compiles fine, but with the build script it somehow activates the `use_std` feature of `libc`: ``` rustc --crate-name libc /…/.cargo/registry/src/github.com-[…]/libc-0.2.42/src/lib.rs --crate-type lib...