Skip to content

Consider opting for unsafe_op_in_unsafe_fn #285

Closed

Description

@nbdd0121

#![warn(unsafe_op_in_unsafe_fn)] will no longer make unsafe fn imply a unsafe {} surrounding the body. We should consider switching it on to make all unsafe operations explicit, even inside unsafe fn. This will ensure that all operations in unsafe fn still have their invariants audited and upheld.

This feature is stablised in Rust 1.52 so we may want a newer version of Rust nightly.

Activity

  1. ojeda commented on May 21, 2021

    @ojeda
    Member

    I would definitely want that.

  2. ojeda commented on May 22, 2021

    @ojeda
    Member

    Depends on #135.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    • libRelated to the `rust/` library.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions