Skip to content
This repository was archived by the owner on Jul 3, 2024. It is now read-only.
This repository was archived by the owner on Jul 3, 2024. It is now read-only.

Smarter uniqueing for warnings #84

@Xazax-hun

Description

@Xazax-hun

If we dereference a dangling pointer (pointee went out of scope) multiple times we will get multiple warnings. We unique warnings based on the report location. But in fact, all the errors were the same. So maybe we should have emitted only one warning per pointee out of scope. So maybe, for some warnings, we should use the notes as a uniqueing location instead of the actual warning. The clang static analyzer does something similar for leaks, instead of reporting them on every path, it reports leaks only once per allocation site.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions