Tracking issue for zerocopy #588

Open
opened 2022-02-11 20:04:15 -06:00 by KodrAus · 2 comments
KodrAus commented 2022-02-11 20:04:15 -06:00 (Migrated from github.com)

This issue is a place to keep anybody using the unstable zerocopy feature up-to-date on any changes being made to it.

In order to use zerocopy, you need to opt-in not just to the feature, but to the uuid_unstable RUSTFLAGS configuration too. We can make breaking changes to zerocopy at any point, but still want to be considerate of anybody making use of it, so will try keep open about any version bumps or other breakage that's coming.

This issue is a place to keep anybody using the unstable `zerocopy` feature up-to-date on any changes being made to it. In order to use `zerocopy`, you need to opt-in not just to the feature, but to the `uuid_unstable` RUSTFLAGS configuration too. We can make breaking changes to `zerocopy` at any point, but still want to be considerate of anybody making use of it, so will try keep open about any version bumps or other breakage that's coming.
arctic-alpaca commented 2026-07-01 04:53:59 -05:00 (Migrated from github.com)

@KodrAus As far as I can tell, this issue was closed by mistake since the zerocopy support is still unstable.

@KodrAus As far as I can tell, this issue was closed by mistake since the `zerocopy` support is still unstable.
KodrAus commented 2026-07-01 17:39:19 -05:00 (Migrated from github.com)

Thanks @arctic-alpaca, this should still be open.

Thanks @arctic-alpaca, this should still be open.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-uuid-rs/uuid#588
No description provided.