-
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
Update rls-data for save analysis #45096
Update rls-data for save analysis #45096
Conversation
0.10 -> 0.11 This will allow for more fine-grained save analysis for enum variants (tuple and struct)
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @arielb1 (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. |
Thanks for the PR! We’ll periodically check in on it to make sure that @arielb1 or someone else from the team reviews it soon. |
Thanks for the PR! Can this also update the |
I have some instructions that should help you update the rustfmt submodule. Please let me know in the PR if you run into anything so I can update the instructions before they get merged. |
@alexcrichton I pushed a commit that updates @sunjay Thanks for the tips! They saved me some frustration. |
@bors: r+ |
📌 Commit 218103e has been approved by |
⌛ Testing commit 218103e with merge 33a10f59619a455f8479ac4db5da648ca9f8fd5c... |
💔 Test failed - status-appveyor |
RLS tests failed on Windows.
|
Hmmm...the test failures only happen when running the tests with x.py. Running with I know why |
☔ The latest upstream changes (presumably #45175) made this pull request unmergeable. Please resolve the merge conflicts. |
Can you reproduce with |
Yes. But not while running |
Maybe other dependencies have a slightly different version? I've had great difficulty myself in debugging rls tests historically... I've found though that |
@bors: r+ |
📌 Commit 933b3fb has been approved by |
⌛ Testing commit 933b3fbf9bdeb978f96132c959bf2042b4513c73 with merge 9569d3e0e27f939e9d05c6e44caf06bcf161e085... |
💔 Test failed - status-travis |
|
The failure is an intermittent timing issue with new tests in the RLS. See rust-lang/rls#524 for context. Until the fix is made, would it be reasonable to mark the RLS as "Compiling" instead of "Testing" in |
☔ The latest upstream changes (presumably #44766) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors: r+ |
📌 Commit aba409c has been approved by |
…r=alexcrichton Update rls-data for save analysis rls-data: 0.10 -> 0.11 This will allow for more fine-grained save analysis for enum variants (tuple and struct). The first commit updates rls-data, and makes the changes to dump_visitor. The second commit updates the rls submodule, and removes "members" that were deleted from that update in src/Cargo.toml. Note, that when building the project, rustfmt-nightly was updated in Cargo.lock. If these changes should be excluded, I can revert it. cc/ @nrc
☀️ Test successful - status-appveyor, status-travis |
rls-data: 0.10 -> 0.11
This will allow for more fine-grained save analysis for enum variants (tuple and struct).
The first commit updates rls-data, and makes the changes to dump_visitor. The second commit updates the rls submodule, and removes "members" that were deleted from that update in src/Cargo.toml.
Note, that when building the project, rustfmt-nightly was updated in Cargo.lock. If these changes should be excluded, I can revert it.
cc/ @nrc