-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Fix HashMap not displaying correctly in VS debugger #93626
Conversation
The natvis to render HashMaps was not working correctly in Visual Studio because the type names for tuples changed from `tuple$<A, B>` to `tuple$<A,B>` (notice the missing space). WinDbg and cdb continued to parse this type name which is why no tests in CI broke. VS however is slightly more strict and this caused the visualizer to break. Since we cannot test the VS debugger in CI, I'm not checking in any test changes.
Yuck! 😄 Thanks for the PR, @wesleywiser! @bors r+ rollup=never (excluding from rollups because debuginfo test) |
📌 Commit fa99aaa has been approved by |
⌛ Testing commit fa99aaa with merge ff3d374e48bbe8270a77959efed26c50c332a808... |
💥 Test timed out |
⌛ Testing commit fa99aaa with merge c508b9ada4a130b90672443889efa1729b0b3858... |
💔 Test failed - checks-actions |
@bors retry |
⌛ Testing commit fa99aaa with merge 57c857a05be590bdd03c43d1d799b923892937b0... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry Rustdoc gui test failure |
⌛ Testing commit fa99aaa with merge ca6439d520e13b93559960f5762a172a2a338784... |
💔 Test failed - checks-actions |
@bors retry
|
☀️ Test successful - checks-actions |
Finished benchmarking commit (775e480): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
The natvis to render HashMaps was not working correctly in Visual Studio
because the type names for tuples changed from
tuple$<A, B>
totuple$<A,B>
(notice the missing space). WinDbg and cdb continued toparse this type name which is why no tests in CI broke. VS however is
slightly more strict and this caused the visualizer to break.
Since we cannot test the VS debugger in CI, I'm not checking in any
test changes.
Fixes #92286
r? @michaelwoerister