Skip to content

Release rayon 1.2.1 / rayon-core 1.6.1#709

Merged
bors[bot] merged 6 commits intorayon-rs:masterfrom
cuviper:release-1.2.1
Nov 21, 2019
Merged

Release rayon 1.2.1 / rayon-core 1.6.1#709
bors[bot] merged 6 commits intorayon-rs:masterfrom
cuviper:release-1.2.1

Conversation

@cuviper
Copy link
Member

@cuviper cuviper commented Nov 20, 2019

No description provided.

A couple temporary `[u8; 128]` arrays were uninitialized, and are now
initialized to zeros. This has no measurable affect on the benchmarks
for `par_sort_unstable`.
For both Unix `getrusage` and Windows `GetProcessTimes`, we can pass
`MaybeUninit` pointers to those FFI calls and `assume_init()` afterward.
- Bump to rayon 1.2.1 and rayon-core 1.6.1.
- Increase crossbeam-deque to 0.7.2 to avoid duping crossbeam-utils.
- Increase demo's fixedbitset to 0.2.0 and glium to 0.25.1.
- Regenerate compat-Cargo.lock with the most current versions possible.
@cuviper
Copy link
Member Author

cuviper commented Nov 20, 2019

bors r+

bors bot added a commit that referenced this pull request Nov 20, 2019
709: Release rayon 1.2.1 / rayon-core 1.6.1 r=cuviper a=cuviper



Co-authored-by: Josh Stone <[email protected]>
@bors
Copy link
Contributor

bors bot commented Nov 21, 2019

@bors bors bot merged commit 33e9843 into rayon-rs:master Nov 21, 2019
@cuviper cuviper deleted the release-1.2.1 branch March 11, 2020 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant