Walk through full path in point_at_path_if_possible#115221
Walk through full path in point_at_path_if_possible#115221bors merged 2 commits intorust-lang:masterfrom
point_at_path_if_possible#115221Conversation
413a4d9 to
11dd84b
Compare
This comment has been minimized.
This comment has been minimized.
11dd84b to
13e8b13
Compare
|
@bors r+ |
| LL | <() as Foo<N>>::test() | ||
| | ^^^^^^^^^^^^^^^^^^^^ the trait `Foo<N>` is not implemented for `()` | ||
| | ^ the trait `Foo<N>` is not implemented for `()` |
There was a problem hiding this comment.
Interestingly, I would have expected the span to point at () here, based on the output of the other tests.
There was a problem hiding this comment.
There's some subtlety in the ordering of what params to prefer over others. Right now we prefer non-self params over self params in qpaths, though arguably pointing at either of the params here is good enough.
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (ac89e16): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 631.205s -> 632.821s (0.26%) |
We already had sufficient information to point at the
[u8]inOption::<[u8]>::None(thefallback_param_to_point_atparameter), we just were neither using it nor walking through hir paths sufficiently to encounter it.This should alleviate the need to add additional logic to extract params in a somewhat arbitrary manner of looking at the grandparent def path: #115219 (comment)
r? @estebank