Skip to content

Remove unsafe uses of copy_nonoverlapping #557

New issue
New issue
Closed
Closed
Remove unsafe uses of copy_nonoverlapping#557
Labels
bugSomething isn't working
Milestone
0.1.0

Description

@andygrove
andygrove
opened on Jun 11, 2024

Describe the bug

We have some uses of std::ptr::copy_nonoverlapping where we do not check the precondition that the pointers must be properly aligned, and we need to address this since it is a safety issue and also prevents us from supporting Rust 1.78.

Steps to reproduce

No response

Expected behavior

No response

Additional context

No response

Activity

  1. andygrove
    added
    bugSomething isn't working
    on Jun 11, 2024
  2. andygrove
    added this to the 0.2.0 milestone on Jun 11, 2024

  3. andygrove commented on Jun 14, 2024

    @andygrove
    andygrove
    on Jun 14, 2024
    MemberAuthor

    This was fixed by #558

  4. andygrove
    closed this as completedon Jun 14, 2024
  5. andygrove
    modified the milestones: 0.2.0, 0.1.0 on Jun 14, 2024
  6. coderfender
    added a commit that references this issue on Dec 13, 2025

    Make Comet opt-in but with all features enabled by default (apache#557)

    bbb838f
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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions