Uh oh!
There was an error while loading. Please reload this page.
bump crossbeam-epoch dependency - #62974
Conversation
rust-highfive
commented
Jul 25, 2019
(rust_highfive has picked a reviewer for you, use r? to override) |
alexcrichton
commented
Jul 25, 2019
@bors: r+ |
bors
commented
Jul 25, 2019
📌 Commit c7a599e has been approved by |
RalfJung
commented
Jul 25, 2019
@alexcrichton do you know about the rustc-rayon situation? It looks like an ancient version of rayon, and is responsible for pulling in ancient versions of other stuff, including crossbeam. |
alexcrichton
commented
Jul 25, 2019
I do not myself, no, but @Zoxc would likely know more |
Zoxc
commented
Jul 25, 2019
|
@Zoxc oh, I was looking at the repo https://github.com/rust-lang/rustc-rayon which has not been changed since forever (at least its default branch, which I would expect to be the basis for the releases as that's where crates.io links). Seems like crates.io and that repo got out-of-sync?
Now there is the incentive to get the broken old |
Zoxc
commented
Jul 25, 2019
No, the default branch is the latest there. github doesn't display when it was last changed though. |
RalfJung
commented
Jul 25, 2019
It says "Latest commit 4b574ba on Apr 25, 2018 ", am I misinterpreting that? |
@RalfJung open |
RalfJung
commented
Jul 26, 2019
@mati865 thanks! I didn't even know that this is the push date GH shows there, but it makes sense now. :) |
bump crossbeam-epoch dependency The new crossbeam-epoch release depends on a memoffset with a whole bunch of soundness holes fixed. The old memoffset is still indirectly depended on (at least) by rustc-rayon, though -- a crate that looks rather unmaintained (no change in more than a year).
bump crossbeam-epoch dependency The new crossbeam-epoch release depends on a memoffset with a whole bunch of soundness holes fixed. The old memoffset is still indirectly depended on (at least) by rustc-rayon, though -- a crate that looks rather unmaintained (no change in more than a year).
bump crossbeam-epoch dependency The new crossbeam-epoch release depends on a memoffset with a whole bunch of soundness holes fixed. The old memoffset is still indirectly depended on (at least) by rustc-rayon, though -- a crate that looks rather unmaintained (no change in more than a year).
Rollup of 4 pull requests Successful merges: - #62550 (Implement RFC 2707 + Parser recovery for range patterns) - #62759 (Actually add rustc-guide to toolstate, don't fail builds for the guide) - #62809 (rustc: Update wasm32 support for LLVM 9) - #62974 (bump crossbeam-epoch dependency) Failed merges: r? @ghost
bump crossbeam-epoch dependency The new crossbeam-epoch release depends on a memoffset with a whole bunch of soundness holes fixed. The old memoffset is still indirectly depended on (at least) by rustc-rayon, though -- a crate that looks rather unmaintained (no change in more than a year).
Rollup of 8 pull requests Successful merges: - #62550 (Implement RFC 2707 + Parser recovery for range patterns) - #62759 (Actually add rustc-guide to toolstate, don't fail builds for the guide) - #62806 (Fix few Clippy warnings) - #62974 (bump crossbeam-epoch dependency) - #63051 (Avoid ICE when referencing desugared local binding in borrow error) - #63061 (In which we constantly improve the Vec(Deque) array PartialEq impls) - #63067 (Add test for issue-50900) - #63071 (Allow rustbot to add `F-*` + `requires-nightly`.) Failed merges: r? @ghost
The new crossbeam-epoch release depends on a memoffset with a whole bunch of soundness holes fixed.
The old memoffset is still indirectly depended on (at least) by rustc-rayon, though -- a crate that looks rather unmaintained (no change in more than a year).