Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Stabilize spawning an asynchronous task and convenience methods on ThreadPool #371

Merged
merged 3 commits into from Jun 14, 2017
Merged

Stabilize spawning an asynchronous task and convenience methods on ThreadPool #371

merged 3 commits into from Jun 14, 2017

Commits on Jun 14, 2017

  1. document how to use rayon as well as semver policy

    @nikomatsakis
    nikomatsakis committed Jun 14, 2017
    Copy the full SHA
    a46de7a View commit details
    Browse the repository at this point in the history

  2. adopt new approach to unstable features

    @nikomatsakis
    nikomatsakis committed Jun 14, 2017
    Copy the full SHA
    20de1ff View commit details
    Browse the repository at this point in the history

  3. Stabilize a number of APIs: 

    - `rayon_core::ThreadPool::join`
- `rayon_core::ThreadPool::scope`
- `rayon_core::ThreadPool::spawn`
- `rayon_core::spawn` -- runs async task in current (or global) thread-pool

The only one that enables something fundamentally new that wasn't
available in a stable API is `rayon_core::spawn`. The `ThreadPool` APIs
are convenience wrappers around other APIs.

The following APIs remain **unstable**:

- `ThreadPool::global` -- I don't know that we want to expose th `Arc`
  here, although it's no real commitment
- everything related to futures -- that is all planned to change
    @nikomatsakis
    nikomatsakis committed Jun 14, 2017
    Copy the full SHA
    e1b4d8a View commit details
    Browse the repository at this point in the history