John Ericson

There is. But I rather not wait for such language change when we can just move it into `alloc` and wrap in a new type. We could have done that...

@jethrogb Yes. But that's no worse than today when its not even available in `alloc`. While `alloc` is unstable, a stop-gap solution like the newtype need not tie our hands.

type aliases cannot have default type parameters.

Woah I didn't know that was even allowed in stable Rust. @eddyb? Still there are issues: ```rust pub type Result = core::result::Result; fn main() { Ok(()); // fn asdf() ->...

To not break compat, we have to default those method type vars taken from the inherent impl. This isn't possible. We don't have the same problem with variant constructurs since...

That's a good idea if you don't need to worry about other libraries consuming a hash map. My RFC https://github.com/rust-lang/rfcs/pull/2492, which will hopefully get more consideration after the Rust 2018...

@cbeck88 the biggest delay is not due to the scope of that RFC but due to the limit bandwidth of the core team. Even some sort of lang item fix...

Ah I finally get that `SpinWait` is _just_ for spinning + backoff. Yeah it can just be dropped in here, replacing https://github.com/mvdnes/spin-rs/blob/master/src/util.rs, with a feature for the std stuff. For...

Sure, but that's still strictly better than what we have now :)

I'd just pull out 4 (for shifting) into a const for easy finding. Users that wish to tune for their own systems can use Cargo's `[[replace]]` to change the constant.