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

Restore old Future and BackgroundWorker behavior. #1830

Merged
merged 4 commits into from
Aug 16, 2024
Merged

Restore old Future and BackgroundWorker behavior. #1830

merged 4 commits into from
Aug 16, 2024

Commits on Aug 15, 2024

  1. Revert BackgroundWorker to its 8.1.3 version. 

    It looks like we'll want to take `BackgroundWorker` in a different direction, so for the moment it's safest not to change anything about it. That way, there's only one historical version to maintain backwards compatibility with.
    @player-03
    player-03 committed Aug 15, 2024
    Configuration menu
    Copy the full SHA
    d0cef42 View commit details
    Browse the repository at this point in the history

  2. Revert to Future's behavior from 8.1.3. 

    As with `BackgroundWorker`, we're postponing major changes to give us more time to consider.
    @player-03
    player-03 committed Aug 15, 2024
    Configuration menu
    Copy the full SHA
    52931a8 View commit details
    Browse the repository at this point in the history

  3. Remove external link. 

    While I put a lot of effort into that guide, we're changing several things suddenly, and I don't have time to make sure it's up to date.
    @player-03
    player-03 committed Aug 15, 2024
    Configuration menu
    Copy the full SHA
    2866d09 View commit details
    Browse the repository at this point in the history

  4. Future.ready() only works when threads are available.

    @player-03
    player-03 committed Aug 15, 2024
    Configuration menu
    Copy the full SHA
    6873ae1 View commit details
    Browse the repository at this point in the history