rust/tests/ui/macros/best-failure.rs

macro_rules! number {
    (neg false, $self:ident) => { $self };
    ($signed:tt => $ty:ty;) => {
        number!(neg $signed, $self);
        //~^ ERROR no rules expected `$`
    };
}

number! { false => u8; }

fn main() {}
Properly calculate best failure in macro matching Previously, we used spans. This was not good. Sometimes, the span of the token that failed to match may come from a position later in the file which has been transcribed into a token stream way earlier in the file. If precisely this token fails to match, we think that it was the best match because its span is so high, even though other arms might have gotten further in the token stream. We now try to properly use the location in the token stream. 2022-12-11 14:46:30 -06:00			`macro_rules! number {`
			`(neg false, $self:ident) => { $self };`
			`($signed:tt => $ty:ty;) => {`
			`number!(neg $signed, $self);`
Tweak more warnings. Much like the previous commit. I think the removal of "the token" in each message is fine here. There are many more error messages that mention tokens without saying "the token" than those that do say it. 2024-06-24 21:52:15 -05:00			//~^ ERROR no rules expected `$`
Properly calculate best failure in macro matching Previously, we used spans. This was not good. Sometimes, the span of the token that failed to match may come from a position later in the file which has been transcribed into a token stream way earlier in the file. If precisely this token fails to match, we think that it was the best match because its span is so high, even though other arms might have gotten further in the token stream. We now try to properly use the location in the token stream. 2022-12-11 14:46:30 -06:00			`};`
			`}`

			`number! { false => u8; }`

			`fn main() {}`