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

refactor: not using unsafe::zeroed() #5684

Closed
wants to merge 105 commits into from

Conversation

benesjan
Copy link
Contributor

No description provided.

sklppy88 and others added 24 commits April 10, 2024 11:57
…k/refactor/unify-zero-empty-to-default-nr-p4
…k/refactor/unify-zero-empty-to-default-nr-p4
…k/refactor/unify-zero-empty-to-default-nr-p4
…k/refactor/unify-zero-empty-to-default-nr-p4
…k/refactor/unify-zero-empty-to-default-nr-p4
…k/refactor/unify-zero-empty-to-default-nr-p4
Copy link
Contributor Author

benesjan commented Apr 11, 2024

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @benesjan and the rest of your teammates on Graphite Graphite

@benesjan benesjan changed the title refactor: not using unsafe::zeroed() refactor: not using unsafe::zeroed() Apr 11, 2024
@benesjan benesjan changed the base branch from ek/refactor/unify-zero-empty-to-default-nr-p4 to master April 11, 2024 07:16
@benesjan benesjan closed this Apr 11, 2024
@ludamad ludamad deleted the 04-11-refactor_not_using_unsafe_zeroed_ branch August 22, 2024 15:01
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