Make sure formatter errors are emitted by the default Write::write_fmt#31904
Merged
bors merged 1 commit intorust-lang:masterfrom Feb 26, 2016
Merged
Make sure formatter errors are emitted by the default Write::write_fmt#31904bors merged 1 commit intorust-lang:masterfrom
bors merged 1 commit intorust-lang:masterfrom
Conversation
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].
Contributor
|
(rust_highfive has picked a reviewer for you, use r? to override) |
Contributor
Author
|
I now realized I didn't consider the possibility of adding new ErrorKinds (I have no idea when that is appropriate). |
Member
Manishearth
added a commit
to Manishearth/rust
that referenced
this pull request
Feb 26, 2016
…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
bors
added a commit
that referenced
this pull request
Feb 26, 2016
bluss
added
the
relnotes
Contributor
Author
|
Small relnote: Correctly emits formatter errors from |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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::Errorreturn).Now we choose to emit an io::Error with kind Other for formatter errors.
Since this may reveal error returns from
write!()and similar thatpreviously passed silently, it's a kind of a [breaking-change].
Fixes #31879