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

Explicitly document that pod_read_unaligned and try_pod_read_unaligned don't panic on unaligned reads #220

Merged
merged 3 commits into from
Jan 25, 2024

Conversation

hniksic
Copy link
Contributor

@hniksic hniksic commented Jan 24, 2024

Their names make that reasonably clear already, but it doesn't hurt to be explicit. Also, when choosing between *from_bytes(x) and pod_read_unaligned(x), it's good to have a clearly documented criterion.

The PR also adds a couple other cosmetic doc fixes, as separate commits.

…d don't panic on unallowed reads

Their names make that reasonably clear already, but it doesn't hurt to
be explicit. Also, when choosing between `*from_bytes(x)` and
`pod_read_unaligned(x)`, it's good to have a clearly documented
criterion.
Add a couple of missing links, add a missing "like" (consistent with
other similar sentences).
The redundant link emits a warning in `cargo doc`.
@Lokathor Lokathor merged commit 8dc32b1 into Lokathor:main Jan 25, 2024
14 checks passed
@Lokathor
Copy link
Owner

released in bytemuck-1.14.1

@hniksic hniksic changed the title Explicitly document that pod_read_unaligned and try_pod_read_unaligned don't panic on unallowed reads Explicitly document that pod_read_unaligned and try_pod_read_unaligned don't panic on unaligned reads Jan 25, 2024
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