Bump async-std from 1.8.0 to 1.9.0
Created by: dependabot[bot]
Bumps async-std from 1.8.0 to 1.9.0.
Release notes
Sourced from async-std's releases.
v1.9.0
Happy New Year everyone! This patch stabilizes the
async_std::channel
submodule, removes the deprecatedsync::channel
types, and introduces thetokio1
feature.New Channels
As part of our
1.8.0
release last month we introduced the newasync_std::channel
submodule and deprecated the unstableasync_std::sync::channel
types. You can read our full motiviation for this change in the last patch notes. But the short version is that the old channels had some fundamental problems, and thesync
submodule is a bit of a mess.This release of
async-std
promotesasync_std::channel
to stable, and fully removes theasync_std::sync::channel
types. In practice many libraries have already been upgraded to the new channels in the past month, and this will enable much of the ecosystem to switch off "unstable" versions ofasync-std
.use async_std::channel; let (sender, receiver) = channel::unbounded(); assert_eq!(sender.send("Hello").await, Ok(())); assert_eq!(receiver.recv().await, Ok("Hello"));
Tokio 1.0 compat
The Tokio project recently released version 1.0 of their runtime, and the async-std team would like to congratulate the Tokio team on achieving this milestone.
This release of
async-std
adds thetokio1
feature flag, enabling Tokio's TLS constructors to be initialized within theasync-std
runtime. This is in addition to thetokio02
andtokio03
feature flags which we were already exposing.In terms of stability it's worth noting that we will continue to provide support for the
tokio02
,tokio03
, andtokio1
on the current major release line ofasync-std
. These flags are part of our public API, and removing compat support for older Tokio versions is considered a breaking change.Added
... (truncated)
Changelog
Sourced from async-std's changelog.
[1.9.0] - 2021-01-15
This patch stabilizes the
async_std::channel
submodule, removes the deprecatedsync::channel
types, and introduces thetokio1
feature.New Channels
As part of our
1.8.0
release last month we introduced the newasync_std::channel
submodule and deprecated the unstableasync_std::sync::channel
types. You can read our full motiviation for this change in the last patch notes. But the short version is that the old channels had some fundamental problems, and thesync
submodule is a bit of a mess.This release of
async-std
promotesasync_std::channel
to stable, and fully removes theasync_std::sync::channel
types. In practice many libraries have already been upgraded to the new channels in the past month, and this will enable much of the ecosystem to switch off "unstable" versions ofasync-std
.use async_std::channel; let (sender, receiver) = channel::unbounded(); assert_eq!(sender.send("Hello").await, Ok(())); assert_eq!(receiver.recv().await, Ok("Hello"));
Tokio 1.0 compat
The Tokio project recently released version 1.0 of their runtime, and the async-std team would like to congratulate the Tokio team on achieving this milestone.
This release of
async-std
adds thetokio1
feature flag, enabling Tokio's TLS constructors to be initialized within theasync-std
runtime. This is in addition to thetokio02
andtokio03
feature flags which we were already exposing.In terms of stability it's worth noting that we will continue to provide support for the
tokio02
,tokio03
, andtokio1
on the current major release line ofasync-std
. These flags are part of our public API, and removing compat support for older Tokio versions is considered a breaking change.Added
... (truncated)
Commits
-
b210ee3
bump Cargo.toml to 1.9.0 -
171e4f9
Merge pull request #936 from async-rs/1.9.0 -
8fcb243
Add 1.9.0 release notes -
b854b67
Merge pull request #934 from Keruspe/channels -
8274995
stabilize new channels -
b1b8355
Merge pull request #933 from async-rs/remove-old-channel -
8c52387
remove deprecated sync::channel -
684ab18
docs: update cargo-edit link in the installation section -
ac19c66
Update async-global-executor and add tokio feature for tokio 1.0 -
4a3f963
feat: use async-lock for RwLock and Barrier - Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)