-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Fix "Mis-calculated spans" errors from -Z save-analysis
+ refactoring
#43826
Conversation
ccf964c
to
03e107f
Compare
Thanks! |
📌 Commit 03e107f has been approved by |
⌛ Testing commit 03e107fb2a61f50c4469db6e2ea37c2c2668703f with merge bd64db92d92019a4c15cce7416e385e49b411dc2... |
03e107f
to
45fb5ab
Compare
@petrochenkov Sorry the PR-CI had shown failure, due to the new test case trying to write to a read-only file system. I've force-pushed a new commit. Maybe let's ensure the CI shows a green tick before re-r+'ing 🙂.
@bors retry (stop the test, go to the next PR.) |
a9a7b4c
to
a017b07
Compare
@bors r+ |
📌 Commit a017b07 has been approved by |
⌛ Testing commit a017b079e94654af35570d6ddcb5b25bbc797229 with merge 924b9811d1b81b8eefec894e3818e0932673dcaf... |
💔 Test failed - status-appveyor |
6c844bd
to
6715007
Compare
Use the `span` field in PathSegment and TyParam instead. Fix rust-lang#43796. Close rust-lang#41478.
6715007
to
60377e4
Compare
@petrochenkov The Windows error should be fixed now, hopefully. |
@bors r+ |
📌 Commit 60377e4 has been approved by |
…ochenkov Fix "Mis-calculated spans" errors from `-Z save-analysis` + refactoring Removed the path span extraction methods from `SpanUtils`: * spans_with_brackets * spans_for_path_segments * spans_for_ty_params Use the `span` fields in `PathSegment` and `TyParam` instead. (Note that since it processes `ast::Path` not a qualified path (`hir::QPath` / `ast::QSelf`), UFCS path will be flattened: `<Foo as a::b::c::Trait>::D::E::F::g` will be seen as `a::b::c::Trait::D::E::F::g`.) Fix #43796. Close #41478. r? @nrc
☀️ Test successful - status-appveyor, status-travis |
Removed the path span extraction methods from
SpanUtils
:Use the
span
fields inPathSegment
andTyParam
instead.(Note that since it processes
ast::Path
not a qualified path (hir::QPath
/ast::QSelf
), UFCS path will be flattened:<Foo as a::b::c::Trait>::D::E::F::g
will be seen asa::b::c::Trait::D::E::F::g
.)Fix #43796. Close #41478.
r? @nrc