-
Notifications
You must be signed in to change notification settings - Fork 13k
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 #27098
Merged
Merged
Rollup of 7 pull requests #27098
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
Manishearth
commented
Jul 17, 2015
- Successful merges: Preserve escape sequences in documentation comments on macro expansion #26777, Improve register_diagnostics macro #27067, Diagnostics for E0364 and E0365 #27071, Update vec.rs #27081, Clean up some wording around globs. #27091, DRY #27094, doc: add missing space #27095
- Failed merges:
Escape sequences in documentation comments must not be parsed as a normal string when expanding a macro, otherwise some innocent but invalid-escape-sequence-looking comments will trigger an ICE. Although this commit replaces normal string literals with raw string literals in macro expansion, this shouldn't be much a problem considering documentation comments are converted into attributes before being passed to a macro anyways. Fixes rust-lang#25929. Fixes rust-lang#25943.
defaults completely.
improve the 'Unsafety' section of `collections::vec::Vec::<T>::from_raw_parts`.
Globs used to be a feature you'd turn on, but now they're not, so this sounds a bit odd.
…rror, r=pnkfelix Transition to the new object lifetime defaults, replacing the old defaults completely. r? @pnkfelix This is a [breaking-change] as specified by [RFC 1156][1156] (though all cases that would break should have been receiving warnings starting in Rust 1.2). Types like `&'a Box<Trait>` (or `&'a Rc<Trait>`, etc) will change from being interpreted as `&'a Box<Trait+'a>` to `&'a Box<Trait+'static>`. To restore the old behavior, write the `+'a` explicitly. For example, the function: ```rust trait Trait { } fn foo(x: &Box<Trait>) { ... } ``` would be rewritten as: ```rust trait Trait { } fn foo(x: &'a Box<Trait+'a>) { ... } ``` if one wanted to preserve the current typing. [1156]: https://github.com/rust-lang/rfcs/blob/master/text/1156-adjust-default-object-bounds.md
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
@bors r+ p=10 |
📌 Commit 1f0564b has been approved by |
@bors r+ p=10 |
📌 Commit 8638dc7 has been approved by |
bors
added a commit
that referenced
this pull request
Jul 17, 2015
This was referenced Jul 18, 2015
Escape sequences in documentation comments must not be parsed as a normal string when expanding a macro, otherwise some innocent but invalid-escape-sequence-looking comments will trigger an ICE. Although this commit replaces normal string literals with raw string literals in macro expansion, this shouldn't be much a problem considering documentation comments are converted into attributes before being passed to a macro anyways. Fixes rust-lang#25929. Fixes rust-lang#25943.
Added some detailed diagnostics for E0364 and E0365.
improve the 'Unsafety' section of `collections::vec::Vec::<T>::from_raw_parts`.
Globs used to be a feature you'd turn on, but now they're not, so this sounds a bit odd.
Following up on comment from rust-lang#26977. r? @brson
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.