Skip to content

Add std::panic::propagate #30557

New issue

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

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

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 7, 2016
Merged

Add std::panic::propagate #30557

merged 1 commit into from
Jan 7, 2016

Conversation

sfackler
Copy link
Member

@sfackler
Copy link
Member Author

Should this be attached to recover's tracking issue or have its own?

@@ -172,7 +172,7 @@ pub fn panicking() -> bool {
#[inline(never)]
#[no_mangle]
#[allow(private_no_mangle_fns)]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

presumably can remove this allow if the fn is becoming public?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Possibly - not sure how deeply that lint looks. This function is now public within its module, but not public outside of the crate.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right, still required: http://is.gd/Z4qyRE

On Fri, Dec 25, 2015 at 8:37 PM, Steven Fackler [email protected]
wrote:

In src/libstd/sys/common/unwind/mod.rs
#30557 (comment):

@@ -172,7 +172,7 @@ pub fn panicking() -> bool {
#[inline(never)]
#[no_mangle]
#[allow(private_no_mangle_fns)]

Possibly - not sure how deeply that lint looks. This function is now
public within its module, but not public outside of the crate.


Reply to this email directly or view it on GitHub
https://github.com/rust-lang/rust/pull/30557/files#r48444144.

@brson brson added I-nominated T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Dec 29, 2015
@brson
Copy link
Contributor

brson commented Dec 29, 2015

cc @rust-lang/libs

/// panic::propagate(err);
/// }
/// ```
#[unstable(feature = "panic_propagate", reason = "awaiting feedback", issue = "0")]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should have an actual issue before it lands.

@sfackler
Copy link
Member Author

sfackler commented Jan 7, 2016

@bors r=aturon

We discussed this during libs triage today and are okay with it.

@bors
Copy link
Collaborator

bors commented Jan 7, 2016

📌 Commit 022c9c7 has been approved by aturon

@bors
Copy link
Collaborator

bors commented Jan 7, 2016

⌛ Testing commit 022c9c7 with merge 3ed6e9e...

@bors bors merged commit 022c9c7 into rust-lang:master Jan 7, 2016
@aturon aturon removed the I-nominated label Jan 8, 2016
@sfackler sfackler deleted the panic-propagate branch November 26, 2016 05:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants