{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihfq23uxewvme2gsk7zn7ssafg4knz5odz2mallqzbxfftatpmloi",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3micd7xwxd7j2"
  },
  "path": "/t/drop-on-await-point/24119#post_3",
  "publishedAt": "2026-03-30T13:05:45.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "Clippy Lints"
  ],
  "textContent": "> i guess a way that could work is a recursive auto trait that is mutually exclusive with `Future` ? that's a bit strange. should it cover `Coroutine` s as well ?\n\nI currently don't propose any implementation path, but as a general idea. And yes, `Coroutine` as well.\n\n> can you name some ? currently there is no way to ensure one is not held across an await point afaik\n\nMostly mutexes do rely on the fact that they are not held across await points, to prevent deadlocks. Clippy even has lints against it, like Clippy Lints .",
  "title": "Drop on `await` point"
}