Skip to content

po4yka/rust-skills / skills/rust-send-sync

rust-send-sync

Verified

Use when deciding whether a type is Send or Sync, or when rustc rejects a value at a thread or task boundary with "cannot be sent between threads safely", "cannot be shared between threads safely", or "future cannot be sent between threads safely". Also for auto trait rules of references and smart pointers (Arc vs Rc), Mutex vs RwLock payload bounds, why MutexGuard is not Send yet is Sync, PhantomData markers that remove Send or Sync, auto trait leakage from impl Trait and async fn, and E0321. Not for proving a manual unsafe impl Send or Sync; use `rust-unsafe`.

FileKindSize
SKILL.mdskill md11.2 KB
references/auto-trait-proofs.mdmarkdown4.2 KB
references/phantomdata-markers.mdmarkdown2.6 KB
references/rustc-transcripts.mdmarkdown4.4 KB

references/phantomdata-markers.md

View on GitHub
# `PhantomData` markers for `Send` and `Sync`

`PhantomData<X>` inherits `X`'s auto traits exactly, so any std type with the wanted
implementation works as a marker. Pick the marker that removes only what you mean to remove:

| Marker field | `Send` | `Sync` |
| --- | --- | --- |
| `PhantomData<fn() -> T>` | kept | kept |
| `PhantomData<Cell<()>>` | kept | removed |
| `PhantomData<MutexGuard<'static, ()>>` | removed | kept |
| `PhantomData<*const ()>` | removed | removed |

Write `()` in the last three markers. With `T` in its place, "kept" becomes conditional:
`Cell<T>` is `Send` only when `T: Send`, and `MutexGuard<'_, T>` is `Sync` only when `T: Sync`.

A marker that names your own `T` also sets the variance in `T` and the drop-check ownership. The
`rust-variance` skill, when it is installed, owns the table for both; `PhantomData<fn() -> T>`
stays covariant without ownership, and `PhantomData<fn(T) -> T>` is invariant and keeps `Send`
and `Sync` for every `T`.

```rust
use std::cell::Cell;
use std::marker::PhantomData;
use std::sync::MutexGuard;

struct SendNotSync(PhantomData<Cell<()>>);                 // moves threads, does not share
struct SyncNotSend(PhantomData<MutexGuard<'static, ()>>);  // shares, stays on its thread
struct NeitherOne(PhantomData<*const ()>);                 // both removed
struct BothKept<T>(PhantomData<fn() -> T>);                // both kept for every T

fn assert_send<T: Send>() {}
fn assert_sync<T: Sync>() {}
fn main() {
    assert_send::<SendNotSync>();
    assert_sync::<SyncNotSend>();
    assert_send::<BothKept<std::rc::Rc<i32>>>();
    assert_sync::<BothKept<std::rc::Rc<i32>>>();
    let _ = NeitherOne(PhantomData);   // constructs, but neither Send nor Sync
}
```

Rules:

- Reach for `PhantomData<*mut ()>` only when you mean "neither". It is the default reflex and it
  is wrong when you only meant "not shareable": it also blocks moving the value to a worker
  thread, and the diagnostic then names `*mut ()`, a type the reader cannot find in the struct.
- Write `()` inside the marker when the marker only drops an auto trait. A marker that names your
  own parameter also constrains variance: `PhantomData<Cell<T>>` makes the struct invariant in
  `T`, which rejects caller substitutions that look safe.
- `PhantomData<MutexGuard<'static, T>>` goes further than the other four markers. `MutexGuard<'a,
  T>` is declared `T: ?Sized + 'a`, so a naked `T` in this marker forces `T: 'static` on the
  struct, and rustc rejects the definition with `error[E0310]`. Write `MutexGuard<'static, ()>`
  for the auto trait effect, and name `T` in a second marker.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall