-
Notifications
You must be signed in to change notification settings - Fork 13.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[DONT MERGE] Always validate HIR ID for TypeckTables #64262
[DONT MERGE] Always validate HIR ID for TypeckTables #64262
Conversation
...and not only with `debug_assertions` compiled in
@bors try |
…es, r=<try> [DONT MERGE] Always validate HIR ID for TypeckTables ...and not only with `debug_assertions` compiled in - #64250 (comment). cc @Mark-Simulacrum @michaelwoerister Let's do a try run to see if this impacts perf anyhow? r? @ghost
💔 Test failed - checks-azure |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Fixes an issue where we did not nest tables correctly when resolving associated types in formal argument/return type positions
@bors try |
…es, r=<try> [DONT MERGE] Always validate HIR ID for TypeckTables ...and not only with `debug_assertions` compiled in - #64250 (comment). cc @Mark-Simulacrum @michaelwoerister Let's do a try run to see if this impacts perf anyhow? r? @ghost
Uh, if the dist run failed then no artifacts would've been generated AFAIK. |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
☀️ Try build successful - checks-azure |
@rust-timer build 647e87d |
Success: Queued 647e87d with parent ef54f57, comparison URL. |
Finished benchmarking try commit 647e87d, comparison URL. |
I tried to pick an early base but I could only do with a date start: https://perf.rust-lang.org/compare.html?start=2019-09-06&end=647e87d6d5f99f6a8f2497a7af33393598398b67 (later commits are not available?) Instruction-wise, @Mark-Simulacrum I'd appreciate another set of eyes on the perf results; do these seem reasonable? |
Okay, the immediate results are in and I believe these look like noise, so maybe we can land it? |
Yeah, I'll go ahead and close this PR but the other PR should now not have any performance concerns. |
Performance shouldn't be impacted (see [1] for a perf run) and this should allow us to catch more bugs, e.g. [2] and [3]. [1]: rust-lang#64262 [2]: rust-lang#64250 [3]: rust-lang#57298
Performance shouldn't be impacted (see [1] for a perf run) and this should allow us to catch more bugs, e.g. [2] and [3]. [1]: rust-lang#64262 [2]: rust-lang#64250 [3]: rust-lang#57298
...and not only with
debug_assertions
compiled in - #64250 (comment).cc @Mark-Simulacrum @michaelwoerister
Let's do a try run to see if this impacts perf anyhow?
r? @ghost