Skip to content

Rust: low percentage of macro calls with call targets #20643

@hashcatHitman

Description

@hashcatHitman

Description of the issue
I'm getting a warning about low-quality scans for Rust (see image below). This is in my public project base, which contains very little actual code.

Image

Given that the complaint is about a low percentage of macro calls with call targets, this may be related to #19966 and/or #19982. That said, I don't see any explicit warnings about macro expansion in the logs of the action.

The only macro I use is println!, which I can expand just fine with rust-analyzer locally (as seems to have been suggested in this discussion).

I am new to using CodeQL on anything, so it's entirely possible I'm just being silly here. But given how little is actually going on in my repository code wise, I thought this might be a good indicator of some edge case failure.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions