Skip to content

Commit

Permalink
Merge pull request #373 from nikomatsakis/rayon-v0.8.1
Browse files Browse the repository at this point in the history
release rayon 0.8.1, rayon-core 1.2.0
  • Loading branch information
nikomatsakis committed Jun 14, 2017
2 parents 248113e + f3bc71c commit c95b859
Show file tree
Hide file tree
Showing 4 changed files with 28 additions and 4 deletions.
4 changes: 2 additions & 2 deletions Cargo.toml
@@ -1,6 +1,6 @@
[package]
name = "rayon"
version = "0.8.0"
version = "0.8.1"
authors = ["Niko Matsakis <niko@alum.mit.edu>",
"Josh Stone <cuviper@gmail.com>"]
description = "Simple work-stealing parallelism for Rust"
Expand All @@ -13,7 +13,7 @@ members = ["rayon-demo", "rayon-core"]
exclude = ["ci"]

[dependencies]
rayon-core = { version = "1.1", path = "rayon-core" }
rayon-core = { version = "1.2", path = "rayon-core" }

[dev-dependencies]
compiletest_rs = "0.2.1"
Expand Down
2 changes: 1 addition & 1 deletion README.md
Expand Up @@ -40,7 +40,7 @@ as:

```rust
[dependencies]
rayon = 0.8.0
rayon = 0.8.1
```

and then add the following to to your `lib.rs`:
Expand Down
24 changes: 24 additions & 0 deletions RELEASES.md
@@ -1,3 +1,27 @@
# Release rayon 0.8.1 / rayon-core 1.2.0

- The following core APIs are being stabilized:
- `rayon::spawn()` -- spawns a task into the Rayon threadpool; as it
is contained in the global scope (rather than a user-created
scope), the task cannot capture anything from the current stack
frame.
- `ThreadPool::join()`, `ThreadPool::spawn()`, `ThreadPool::scope()`
-- convenience APIs for launching new work within a thread-pool.
- The various iterator adapters are now tagged with `#[must_use]`
- Parallel iterators now offer a `for_each_with` adapter, similar to
`map_with`.
- We are adopting a new approach to handling the remaining unstable
APIs (which primarily pertain to futures integration). As awlays,
unstable APIs are intended for experimentation, but do not come with
any promise of compatibility (in other words, we might change them
in arbitrary ways in any release). Previously, we designated such
APIs using a Cargo feature "unstable". Now, we are using a regular
`#[cfg]` flag. This means that to see the unstable APIs, you must do
`RUSTFLAGS='--cfg rayon_unstable' cargo build`. This is
intentionally inconvenient; in particular, if you are a library,
then your clients must also modify their environment, signaling
their agreement to instability.

# Release rayon 0.8.0 / rayon-core 1.1.0

## Rayon 0.8.0
Expand Down
2 changes: 1 addition & 1 deletion rayon-core/Cargo.toml
@@ -1,6 +1,6 @@
[package]
name = "rayon-core"
version = "1.1.0"
version = "1.2.0"
authors = ["Niko Matsakis <niko@alum.mit.edu>",
"Josh Stone <cuviper@gmail.com>"]
description = "Core APIs for Rayon"
Expand Down

0 comments on commit c95b859

Please sign in to comment.