Skip to content

chore(quest): plan a byte pointer past its view in ts-unsafe #456

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.

Sign up for GitHub

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

Merged
moq-bot merged 2 commits into from
Nov 2, 2026
Merged

chore(quest): plan a byte pointer past its view in ts-unsafe #456

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bd3353b
chore(quest): plan a byte pointer past its view in ts-unsafe
kixelated Nov 2, 2026
6f7f90a
quest land: merge tested base
Nov 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions quest/m3/ts-unsafe.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,10 @@ none of its own `unsafe`.
by buffer and byte offset closes it.
- `UnsafeCell::raw_get`, `from_mut`, and `replace`, refused with their span: none is in
moq's census at the pin.
- A byte pointer moved past its own `Uint8Array` view into the rest of the buffer, such as
a byte vector's spare capacity: it fails loudly at run time, since each view knows only
its own range. One shared view per buffer, with each pointer's byte offset into it,
closes it. Found by [#455](https://github.com/moq-dev/rust2/pull/455).
- A slice's pointer cast to an array's of its length, `*(s as *const [u8] as *const
[u8; N])`, which `bytes`' `Buf::get_u16` and wider read a crate's own buffer through
([#222](https://github.com/moq-dev/rust2/pull/222)): the bytes keep their type, so
Expand Down