Skip to content

Lint suggestion: unsafe should require a // Safety comment #4828

@Lucretiel

Description

@Lucretiel

I was pleased to see that there's a clippy lint for requiring a /// # Safety header in exposed unsafe methods; my suggestion is to go further and add a lint requiring safety commentary in all unsafe { } blocks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions