-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make rand compile with nightly #93
Conversation
👍 for reporting this upstream (I would do it but I don't know enough about this particular regression). |
Same as #92 |
@numerodix 👍 you were a little bit faster. I'll close my PR. It's already reported upstream |
I filed the regression in Rust. We should probably fix that. |
@fhahn Oh, you said it was reported upstream. Do you have a link? |
@brson: I think it's rust-lang/rust#30713. |
rust-lang/rust#30733 should fix this |
Can we merge this thing? New nightlies have not landed for the last couple of days, and I believe this is blocking getting serde in a good place. cc @erickt |
It was fixed in Rust a few hours ago, so tomorrow it should build without the patch. At least, that's what I thought. On Jan 7, 2016, 13:21 -0500, Steven Facklernotifications@github.com, wrote:
|
👍 on merging anyway - fixing |
The nightlies are broken so this still isn't fixed. Could someone merge and publish this? A lot of crates are broken because of this. |
Looks like #92 beat this to the bunch, so closing, but thanks! |
The linux dist bot timed out :( On Sat, Jan 9, 2016 at 12:58 PM, Alex Crichton notifications@github.com
|
When compiling
rand
with the current nightly it fails because Rustc cannot find the correct type for the second operand of the wrapping shift operation:This PR adds an explicit cast to
usize
to fix this, but this may be a regression worth reporting upstream?