84b9145076
Track span of function in method calls, and use this in #[track_caller] Fixes #69977 When we parse a chain of method calls like `foo.a().b().c()`, each `MethodCallExpr` gets assigned a span that starts at the beginning of the call chain (`foo`). While this is useful for diagnostics, it means that `Location::caller` will return the same location for every call in a call chain. This PR makes us separately record the span of the function name and arguments for a method call (e.g. `b()` in `foo.a().b().c()`). This `Span` is passed through HIR lowering and MIR building to `TerminatorKind::Call`, where it is used in preference to `Terminator.source_info.span` when determining `Location::caller`. This new span is also useful for diagnostics where we want to emphasize a particular method call - for an example, see https://github.com/rust-lang/rust/pull/72389#discussion_r436035990 |
||
|---|---|---|
| .. | ||
| ast | ||
| attr | ||
| expand | ||
| util | ||
| ast.rs | ||
| build.rs | ||
| Cargo.toml | ||
| crate_disambiguator.rs | ||
| entry.rs | ||
| lib.rs | ||
| mut_visit.rs | ||
| node_id.rs | ||
| ptr.rs | ||
| README.md | ||
| token.rs | ||
| tokenstream.rs | ||
| visit.rs | ||
The rustc_ast crate contains those things concerned purely with syntax
– that is, the AST ("abstract syntax tree"), parser, pretty-printer,
lexer, macro expander, and utilities for traversing ASTs.
For more information about how these things work in rustc, see the rustc dev guide: