Nicholas Nethercote d1f05fd184 Distinguish the two kinds of token range. ... When collecting tokens there are two kinds of range: - a range relative to the parser's full token stream (which we get when we are parsing); - a range relative to a single AST node's token stream (which we use within `LazyAttrTokenStreamImpl` when replacing tokens). These are currently both represented with `Range<u32>` and it's easy to mix them up -- until now I hadn't properly understood the difference. This commit introduces `ParserRange` and `NodeRange` to distinguish them. This also requires splitting `ReplaceRange` in two, giving the new types `ParserReplacement` and `NodeReplacement`. (These latter two names reduce the overloading of the word "range".) The commit also rewrites some comments to be clearer. The end result is a little more verbose, but much clearer.		2024-08-01 19:30:40 +10:00
..
src	Distinguish the two kinds of token range.	2024-08-01 19:30:40 +10:00
Cargo.toml	Clean up rustc_*/Cargo.toml.	2023-10-30 08:46:02 +11:00
messages.ftl	Rollup merge of #127853 - folkertdev:naked-function-error-messages, r=bjorn3	2024-07-28 08:57:16 +02:00