about summary refs log tree commit diff
path: root/src/librustdoc/html/static/js/source-script.js
diff options
context:
space:
mode:
authorMichael Goulet <michael@errs.io>2022-06-23 14:39:07 -0700
committerGitHub <noreply@github.com>2022-06-23 14:39:07 -0700
commit3b68700d0ce297e48c6448f27d156d5f461d64e9 (patch)
tree3b0ad77acef4869134e68b7e9b28f59aac09944c /src/librustdoc/html/static/js/source-script.js
parent413e350f87fafeea3da13fc98337c632c4cfcd70 (diff)
parentf924e74fb1c238b0e6c06c23b51c087f1e6aa0d5 (diff)
downloadrust-3b68700d0ce297e48c6448f27d156d5f461d64e9.tar.gz
rust-3b68700d0ce297e48c6448f27d156d5f461d64e9.zip
Rollup merge of #98269 - compiler-errors:provide-more-segment-res, r=petrochenkov
Provide a `PathSegment.res` in more cases

I find that in many cases, the `res` associated with a `PathSegment` is `Res::Err` even though the path was fully resolved. A few diagnostics use this `res` and their error messages suffer because of the lack of resolved segment.

This fixes it a bit, but it's obviously not complete and I'm not exactly sure if it's correct.
Diffstat (limited to 'src/librustdoc/html/static/js/source-script.js')
0 files changed, 0 insertions, 0 deletions