Skip to content

Clarify semantics of auto traits. #326

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
May 3, 2018
Merged

Conversation

alercah
Copy link
Contributor

@alercah alercah commented May 3, 2018

Fixes #257.

implement it for types that could use the implementation except that they do not
meet the requisite trait bounds. For instance, the standard library implements
`Send` for all `&T` where `T` is `Sync`; this means that the compiler will not
implement `Send` for `&T` for if `T` is `Send` but not `Sync`.
Copy link
Contributor

Choose a reason for hiding this comment

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

"for if"?

library.

Auto traits may be added as an additional bound to any [trait object], even
though normally only one trait is allowed. For instance, `Box<Debug + Send +
Copy link
Contributor

Choose a reason for hiding this comment

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

Wanna add a dyn here?

@alercah
Copy link
Contributor Author

alercah commented May 3, 2018

Fixed issues.

@Havvy Havvy merged commit 5b2346a into rust-lang:master May 3, 2018
@Havvy
Copy link
Contributor

Havvy commented May 3, 2018

💟 Thanks!

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.

2 participants