Add minimal support for rustc-rayon#212
Conversation
bluss
left a comment
There was a problem hiding this comment.
looks good to me, seems sensible.
|
This makes me wonder about more hacky ideas, could rustc just patch in an alternative fork of rayon from the top of its cargo projects? I don't think the cargo patch feature can do exactly that, at least not without requiring version/crate name to stay identical. |
|
Cargo patches affect the whole workspace, and I'm not sure we would want to force that fork everywhere since it lags behind. Really, we should do away with that fork, but that requires more work and nobody is really using the parallel rustc anyway... |
|
Yes I guess the fork would have to be a lot more careful about exactly what it's changing if it should work, it would need to be designed for being used that way. |
|
This is amazing! Thank you @cuviper. :) |
|
Yes, this has |
|
Confirmed on zulip that it is working with the "rustc-rayon" feature properly enabled. :) I'm merging this, then I'll check other pending PRs and see about publishing a release. |
This adds basic
IntoParallelIteratorsupport for therustc-rayonfork ofrayon, as needed by rust-lang/rust#90842 (cc @pierwill). The optional dependency is commented as "internal" forrustc's use alone, and we should feel free to make breaking changes like semver-bumps in coordination with compiler updates.