Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Alexendoo (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

I'm not a clippy expert but this fix looks like a hack to me. Why don't we want to report these? The bug I reported is that this FP happens even when I put an #[allow(...)] on the expression.

@tamird I think you misunderstand my point. This FP happens because clippy is linting the panicked message generated by assert!. So adding an #[allow(...)] on the expression will not affected the generated string literal.

fn test_parse() {
    if !parse(#[allow(clippy::literal_string_with_formatting_args)] "foo {:}").is_err()
            {
            ::core::panicking::panic("assertion failed: parse(#[allow(clippy::literal_string_with_formatting_args)] \"foo {:}\").is_err()") // This is line is causing the FP
        };
}

I'm not sure this is the right fix. The problem here was that I was working on dummy spans, which is why the lint seemed to be emitted on completely unrelated code. I opened #13953.

Closed in favor of #13953