-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Rollup of 7 pull requests #32126
Merged
Merged
Rollup of 7 pull requests #32126
Conversation
This file contains 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
Member
steveklabnik
commented
Mar 8, 2016
- Successful merges: Clarify the semantics of enum discriminants #31772, reference.md: clarify the limitation of type alias on an enum #32083, Fix typos - mismatching parentheses in comments #32084, Update syntax index with OpAssign traits #32092, Clarify documentation for string slicing (Index impls) #32099, Fixed link in ownership documentation #32103, Update a spelling inconsistency #32115
- Failed merges:
Changed "[vector]" to a link to the vector documentation.
- Mention the sugared syntax for the implementations, since it's not apparent from the docs that `Index<Range<usize>>` corresponds to `&self[a..b]`. - Be specific in that start <= end and end <= len
Cf. rust-lang#26264 Signed-off-by: NODA, Kai <nodakai@gmail.com>
L26: "zero cost" -> "zero-cost"
Clarify the semantics of enum discriminants cf. https://doc.rust-lang.org/error-index.html#E0082 > The default type for enum discriminants is isize, but it can be adjusted by adding the repr attribute to the enum declaration. It would be great if anyone could check my English.
…, r=nikomatsakis reference.md: clarify the limitation of type alias on an enum Tentatively define the current behavior as the specification. Cf. rust-lang#26264, rust-lang#28556, rust-lang#30936
…crichton Fix typos - mismatching parentheses in comments Fixes mismatching parentheses in the comments of precision example. r? @steveklabnik
…bnik Update syntax index with OpAssign traits book: Update syntax index with OpAssign traits The traits are stable from Rust 1.8.
…chton Clarify documentation for string slicing (Index impls) Clarify documentation for string slicing (Index impls) - Mention the sugared syntax for the implementations, since it's not apparent from the docs that `Index<Range<usize>>` corresponds to `&self[a..b]`. - Be specific in that start <= end and end <= len This is just one fix in response to rust-lang#32057
Fixed link in ownership documentation Changed "[vector]" to a link to the vector documentation.
Update a spelling inconsistency L26: "zero cost" -> "zero-cost"
@bors: r+ p=1 |
📌 Commit 33fe4d1 has been approved by |
bors
added a commit
that referenced
this pull request
Mar 9, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.