Skip to content
This repository was archived by the owner on Mar 23, 2021. It is now read-only.

Commit d44ef78

Browse files
Merge #1705
1705: Bump async-std from 1.1.0 to 1.2.0 r=mergify[bot] a=dependabot-preview[bot] Bumps [async-std](https://github.com/async-rs/async-std) from 1.1.0 to 1.2.0. <details> <summary>Release notes</summary> *Sourced from [async-std's releases](https://github.com/async-rs/async-std/releases).* > ## v1.2.0 > [API Documentation](https://docs.rs/async-std/1.2.0/async-std) > > This patch includes some minor quality-of-life improvements, introduces a > new `Stream::unzip` API, and adds verbose errors to our networking types. > > This means if you can't connect to a socket, you'll never have to wonder again > *which* address it was you couldn't connect to, instead of having to go through > the motions to debug what the address was. > > ## Example > > Unzip a stream of tuples into two collections: > > ```rust > use async_std::prelude::*; > use async_std::stream; > > let s = stream::from_iter(vec![(1,2), (3,4)]); > > let (left, right): (Vec<_>, Vec<_>) = s.unzip().await; > > assert_eq!(left, [1, 3]); > assert_eq!(right, [2, 4]); > ``` > > ## Added > > - Added `Stream::unzip` as "unstable". > - Added verbose errors to the networking types. > > ## Changed > > - Enabled CI on master branch. > - `Future::join` and `Future::try_join` can now join futures with different > output types. > > ## Fixed > > - Fixed the docs and `Debug` output of `BufWriter`. > - Fixed a bug in `Stream::throttle` that made it consume too much CPU. </details> <details> <summary>Changelog</summary> *Sourced from [async-std's changelog](https://github.com/async-rs/async-std/blob/master/CHANGELOG.md).* > # [1.2.0] - 2019-11-27 > > [API Documentation](https://docs.rs/async-std/1.2.0/async-std) > > This patch includes some minor quality-of-life improvements, introduces a > new `Stream::unzip` API, and adds verbose errors to our networking types. > > This means if you can't connect to a socket, you'll never have to wonder again > *which* address it was you couldn't connect to, instead of having to go through > the motions to debug what the address was. > > ## Example > > Unzip a stream of tuples into two collections: > > ```rust > use async_std::prelude::*; > use async_std::stream; > > let s = stream::from_iter(vec![(1,2), (3,4)]); > > let (left, right): (Vec<_>, Vec<_>) = s.unzip().await; > > assert_eq!(left, [1, 3]); > assert_eq!(right, [2, 4]); > ``` > > ## Added > > - Added `Stream::unzip` as "unstable". > - Added verbose errors to the networking types. > > ## Changed > > - Enabled CI on master branch. > - `Future::join` and `Future::try_join` can now join futures with different > output types. > > ## Fixed > > - Fixed the docs and `Debug` output of `BufWriter`. > - Fixed a bug in `Stream::throttle` that made it consume too much CPU. </details> <details> <summary>Commits</summary> - [`9627826`](async-rs/async-std@9627826) Bump the version to 1.2.0 - [`4ed15d6`](async-rs/async-std@4ed15d6) Fix links in the changelog - [`0165d7f`](async-rs/async-std@0165d7f) Add missing items to the changelog - [`dba4166`](async-rs/async-std@dba4166) 1.2.0 ([#589](https://github-redirect.dependabot.com/async-rs/async-std/issues/589)) - [`6800566`](async-rs/async-std@6800566) fix Stream::throttle hot loop ([#584](https://github-redirect.dependabot.com/async-rs/async-std/issues/584)) - [`794e331`](async-rs/async-std@794e331) Refactor join type ([#577](https://github-redirect.dependabot.com/async-rs/async-std/issues/577)) - [`63f7ea3`](async-rs/async-std@63f7ea3) Merge pull request [#587](https://github-redirect.dependabot.com/async-rs/async-std/issues/587) from async-rs/contributing - [`46cafff`](async-rs/async-std@46cafff) Merge pull request [#571](https://github-redirect.dependabot.com/async-rs/async-std/issues/571) from killercup/more-errors - [`0f30ab8`](async-rs/async-std@0f30ab8) Fix the docs and Debug output of BufWriter. ([#588](https://github-redirect.dependabot.com/async-rs/async-std/issues/588)) - [`e66e2e2`](async-rs/async-std@e66e2e2) link to our contribution guidelines - Additional commits viewable in [compare view](async-rs/async-std@v1.1.0...v1.2.0) </details> <br /> [![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=async-std&package-manager=cargo&previous-version=1.1.0&new-version=1.2.0)](https://dependabot.com/compatibility-score.html?dependency-name=async-std&package-manager=cargo&previous-version=1.1.0&new-version=1.2.0) You can trigger a rebase of this PR by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in the `.dependabot/config.yml` file in this repo: - Update frequency - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
2 parents e9471e7 + 00388da commit d44ef78

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Cargo.lock

Lines changed: 3 additions & 3 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)