std: Destabilize the internals of panic!#24212
Merged
bors merged 2 commits intorust-lang:masterfrom Apr 9, 2015
Merged
Conversation
Now that we have a `#[allow_internal_unstable]` attribute for macros there's no need for these two `begin_unwind` functions to be stable. Right now the `panic!` interface is the only one we wish to stabilize, so remove the stability markers from these functions. While this is a breaking change, it is highly unlikely to break any actual code. It is recommended to use the `panic!` macro instead if it breaks explicit calls into `std::rt`. [breaking-change] cc rust-lang#24208
Contributor
|
r? @huonw (rust_highfive has picked a reviewer for you, use r? to override) |
Member
There was a problem hiding this comment.
Do these need explicit #[unstable] annotations?
Contributor
There was a problem hiding this comment.
unstable inherits (in this case from std::rt).
Contributor
|
@bors r+ |
Collaborator
|
📌 Commit 65e3f03 has been approved by |
Contributor
|
Aren't the pretty printing tests going to fail? #23616. |
Member
Author
|
@rprichard you are most correct! re-r? @huonw, I just deleted |
Contributor
|
@bors r+ |
Collaborator
|
📌 Commit 704f628 has been approved by |
704f628 to
f4270c8
Compare
Member
Author
This commit removes pretty-expanded from all tests that wind up calling panic! one way or another now that its internals are unstable.
f4270c8 to
ec7c800
Compare
Member
Author
Manishearth
added a commit
to Manishearth/rust
that referenced
this pull request
Apr 9, 2015
…nd, r=huonw Now that we have a `#[allow_internal_unstable]` attribute for macros there's no need for these two `begin_unwind` functions to be stable. Right now the `panic!` interface is the only one we wish to stabilize, so remove the stability markers from these functions. While this is a breaking change, it is highly unlikely to break any actual code. It is recommended to use the `panic!` macro instead if it breaks explicit calls into `std::rt`. [breaking-change] cc rust-lang#24208
Manishearth
added a commit
to Manishearth/rust
that referenced
this pull request
Apr 9, 2015
…nd, r=huonw Now that we have a `#[allow_internal_unstable]` attribute for macros there's no need for these two `begin_unwind` functions to be stable. Right now the `panic!` interface is the only one we wish to stabilize, so remove the stability markers from these functions. While this is a breaking change, it is highly unlikely to break any actual code. It is recommended to use the `panic!` macro instead if it breaks explicit calls into `std::rt`. [breaking-change] cc rust-lang#24208
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
6 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.
Now that we have a
#[allow_internal_unstable]attribute for macros there's noneed for these two
begin_unwindfunctions to be stable. Right now thepanic!interface is the only one we wish to stabilize, so remove the stability markers
from these functions.
While this is a breaking change, it is highly unlikely to break any actual code.
It is recommended to use the
panic!macro instead if it breaks explicit callsinto
std::rt.[breaking-change]
cc #24208