Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fn mem::zeroed: Replace most uses with Default::default() #994

Merged
merged 2 commits into from
Apr 23, 2024

Conversation

kkysen
Copy link
Collaborator

@kkysen kkysen commented Apr 23, 2024

No description provided.

@rinon rinon self-assigned this Apr 23, 2024
@kkysen kkysen force-pushed the kkysen/backport-itutt35-vec branch from 9fbd679 to d2ae68a Compare April 23, 2024 19:02
@kkysen kkysen force-pushed the kkysen/remove-most-mem-zeroed branch from cec16c0 to 72bdf3e Compare April 23, 2024 19:02
@kkysen kkysen force-pushed the kkysen/backport-itutt35-vec branch from d2ae68a to 1c24cee Compare April 23, 2024 19:05
@kkysen kkysen force-pushed the kkysen/remove-most-mem-zeroed branch from 72bdf3e to 6805593 Compare April 23, 2024 19:05
Base automatically changed from kkysen/backport-itutt35-vec to main April 23, 2024 19:20
…zeroed()`, as previously we were `mem::zeroed()`ing a `RwLock` (UB).
…` except for `scratch`, which is a `union` and a WIP to make safe.
@kkysen kkysen force-pushed the kkysen/remove-most-mem-zeroed branch from 6805593 to 73336f1 Compare April 23, 2024 19:21
@kkysen kkysen merged commit b27620a into main Apr 23, 2024
18 of 19 checks passed
@kkysen kkysen deleted the kkysen/remove-most-mem-zeroed branch April 23, 2024 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants