-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 5 pull requests #41972
Rollup of 5 pull requests #41972
Conversation
frewsxcv
commented
May 13, 2017
- Successful merges: Add markdown-[before|after]-content options #41826, Include the crate's root module in save-analysis #41919, Disallow ._ in float literal. #41946, Reenable opt-level 3 #41967, Update RLS to solve serious crash #41969
- Failed merges: rustc_resolve: don't deny outer type parameters in embedded constants. #41939
This comment is quite old, let's see what would happen with current MSVC.
…, r=frewsxcv Add markdown-[before|after]-content options cc @nical r? @rust-lang/docs
Include the crate's root module in save-analysis r? @eddyb
…loat, r=petrochenkov Disallow ._ in float literal. This patch makes lexer stop parsing number literals before `._`, as well as before `.a`. Underscore itself is still allowed like in `4_000_000.000_000_`. Fixes a half part of rust-lang#41723. The other is `""_`.
Reenable opt-level 3 This comment is quite old, let's see what would happen with current MSVC. Since there's no AppVeyor test for PR, the best way is to try if it get through homu. I don't recommend doing this in roll-up.
Update RLS to solve serious crash As a follow-up to rust-lang/rls#312, this PR contains the fix to the latest experienced RLS crashes, which should hopefully reach the nightly release as soon as possible.
@bors r+ p=10 |
📌 Commit 9d65556 has been approved by |
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @pnkfelix (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
⌛ Testing commit 9d65556 with merge 4d29d84... |
💔 Test failed - status-appveyor |
Spurious? I think? No errors... Odd. @bors retry force
|
@bors retry I have no clue how this syntax really works... |
@Mark-Simulacrum probably #41967 ? |
Maybe, but that looks like it is only MSVC related. |
@bors r- (since @alexcrichton r- a PR this contains) |
@bors retry |