about summary refs log tree commit diff
path: root/src/liballoc
diff options
context:
space:
mode:
authorDylan DPC <dylan.dpc@gmail.com>2020-04-25 18:30:22 +0200
committerGitHub <noreply@github.com>2020-04-25 18:30:22 +0200
commit7b7c63cb7732e5ad5eace294b1c7c2f92beef4a2 (patch)
tree07ab72a6d8d0adf30ca2fd8dad25739b63a524cc /src/liballoc
parentb613c989594f1cbf0d4af1a7a153786cca7792c8 (diff)
parent966a295e8cc210d7b50185d16cb46a7ae1874531 (diff)
downloadrust-7b7c63cb7732e5ad5eace294b1c7c2f92beef4a2.tar.gz
rust-7b7c63cb7732e5ad5eace294b1c7c2f92beef4a2.zip
Rollup merge of #69041 - petrochenkov:stabmodispan, r=Amanieu
proc_macro: Stabilize `Span::resolved_at` and `Span::located_at`

Introduced in https://github.com/rust-lang/rust/pull/47149.
Part of https://github.com/rust-lang/rust/issues/54725.

Motivation: https://github.com/rust-lang/rust/pull/68716#issuecomment-583918919.
Identifiers in proc macros may want to inherit span locations for diagnostics from one tokens (e.g. some tokens from the macro input), but resolve those identifiers from some different location (e.g. from the macro's definition site).
This becomes especially important when multiple resolution locations become available with stabilization of [`Span::mixed_site`](https://github.com/rust-lang/rust/pull/68716).

Why I think this is the right API for setting span's location and hygiene - https://github.com/rust-lang/rust/pull/69041#issuecomment-586644778.

r? @dtolnay
Diffstat (limited to 'src/liballoc')
0 files changed, 0 insertions, 0 deletions