Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Rollup of 8 pull requests #31911

Merged
merged 18 commits into from
Feb 26, 2016
Merged

Rollup of 8 pull requests #31911

merged 18 commits into from
Feb 26, 2016

Conversation

frewsxcv and others added 9 commits February 24, 2016 22:34
It appears in the examples, but is not covered by any of the cases
in the prose description.
Change import a trait suggestion from:

   help: candidate #1: use `std::io::Write`

to

   help: candidate #1: `use std::io::Write`

so that the code can be copied directly.
Previously, if an error was returned from the formatter that did not
originate in an underlying writer error, Write::write_fmt would return
successfully even if the formatting did not complete (was interrupted by
an `fmt::Error` return).

Now we choose to emit an io::Error with kind Other for formatter errors.

Since this may reveal error returns from `write!()` and similar that
previously passed silently, it's a kind of a [breaking-change].
@Manishearth
Copy link
Member Author

@bors r+ p=10

@bors
Copy link
Collaborator

bors commented Feb 26, 2016

📌 Commit 156ed55 has been approved by Manishearth

@Manishearth Manishearth assigned Manishearth and unassigned brson Feb 26, 2016
@bors
Copy link
Collaborator

bors commented Feb 26, 2016

⌛ Testing commit 156ed55 with merge 17c3e75...

@bors
Copy link
Collaborator

bors commented Feb 26, 2016

💔 Test failed - auto-win-msvc-32-opt

Right this information isn't documented anywhere, sticking it into `make tips`
It appears in the examples, but is not covered by any of the cases
in the prose description.
suggest: Put the `use` in suggested code inside the quotes

Change import a trait suggestion from:

       help: candidate #1: use `std::io::Write`

to

       help: candidate #1: `use std::io::Write`

so that the code can be copied directly.

Fixes rust-lang#31864
…xcrichton

Make sure formatter errors are emitted by the default Write::write_fmt

Previously, if an error was returned from the formatter that did not
originate in an underlying writer error, Write::write_fmt would return
successfully even if the formatting did not complete (was interrupted by
an `fmt::Error` return).

Now we choose to emit an io::Error with kind Other for formatter errors.

Since this may reveal error returns from `write!()` and similar that
previously passed silently, it's a kind of a [breaking-change].

Fixes rust-lang#31879
@Manishearth
Copy link
Member Author

@bors r+ force

@bors
Copy link
Collaborator

bors commented Feb 26, 2016

📌 Commit 3c9a268 has been approved by Manishearth

@bors
Copy link
Collaborator

bors commented Feb 26, 2016

⌛ Testing commit 3c9a268 with merge ee8b257...

bors added a commit that referenced this pull request Feb 26, 2016
@bors bors merged commit 3c9a268 into rust-lang:master Feb 26, 2016
@Manishearth Manishearth deleted the rollup branch February 26, 2016 14:54
@Centril Centril added the rollup A PR which is a rollup label Oct 2, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
rollup A PR which is a rollup
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants