{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiew42itsdtyc3gnic7wjrryguqjodccp2sgy3syovni7ekfpqdtd4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mic4jiuvpw42"
  },
  "path": "/t/drop-on-await-point/24119#post_2",
  "publishedAt": "2026-03-30T12:29:04.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Ddystopia:\n\n> Hello, what do you think about potentially adding a language feature that will allow forcing synchronous drop at the `await` boundary, with an error if value is used afterwards\n\ncan you expand on what that would look like ?\n\nDdystopia:\n\n> There exists lots of data structures that rely on the fact that they are not being held across `await` point, and that might help with it.\n\ncan you name some ? currently there is no way to ensure one is not held across an await point afaik.\n\ni 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 ?",
  "title": "Drop on `await` point"
}