Skip to content
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

Make AssertRecoverSafe's field public #32329

Merged
merged 3 commits into from
Mar 19, 2016

Conversation

sfackler
Copy link
Member

It's basically the very definition of a newtype, so we might as well
make things easy on people and let them construct and access it
directly.

r? @aturon

It's basically the very definition of a newtype, so we might as well
make things easy on people and let them construct and access it
directly.
@sfackler sfackler force-pushed the assert-recover-safe-pub branch from 5a53f88 to 74d00bd Compare March 18, 2016 06:37
@aturon
Copy link
Member

aturon commented Mar 18, 2016

r=me after fixes to travis errors.

@sfackler
Copy link
Member Author

@bors r=aturon

@bors
Copy link
Contributor

bors commented Mar 18, 2016

📌 Commit 797d520 has been approved by aturon

@eddyb
Copy link
Member

eddyb commented Mar 19, 2016

@bors rollup

eddyb added a commit to eddyb/rust that referenced this pull request Mar 19, 2016
…=aturon

Make AssertRecoverSafe's field public

It's basically the very definition of a newtype, so we might as well
make things easy on people and let them construct and access it
directly.

r? @aturon
bors added a commit that referenced this pull request Mar 19, 2016
Rollup of 14 pull requests

- Successful merges: #32265, #32269, #32271, #32288, #32308, #32316, #32319, #32321, #32327, #32329, #32332, #32337, #32342, #32347
- Failed merges:
@bors bors merged commit 797d520 into rust-lang:master Mar 19, 2016
@sfackler sfackler deleted the assert-recover-safe-pub 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
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants