{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreih3z42lpwjre5i2vkuh266ky75zy76liw63bzukmq5pddbmslumkq",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mjk2mptdgro2"
  },
  "path": "/t/code-bloat-caused-by-lack-of-nounwind-attr-on-drop-in-place/24173#post_4",
  "publishedAt": "2026-04-15T13:14:42.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "github.com/rust-lang/rfcs",
    "Don't allow unwinding from Drop impls (#3288)",
    "Amanieu",
    "+332\n-0",
    "…"
  ],
  "textContent": "There are proposals to abort when drop panics, at which point all drop functions could be marked as non unwinding.\n\ngithub.com/rust-lang/rfcs\n\n####  Don't allow unwinding from Drop impls (#3288)\n\n`master` ← `Amanieu:panic-in-drop`\n\nopened 01:02AM - 05 Jul 22 UTC\n\n\n\n            Amanieu\n          \n\n\n+332\n-0\n\n\nThis RFC proposes to change this behavior to always abort if a panic attempts to… escape a drop, even if this drop was invoked as part of normal function execution (as opposed to unwinding which already aborts with a double-panic). Previous discussion: https://github.com/rust-lang/lang-team/issues/97 [Rendered](https://github.com/Amanieu/rfcs/blob/panic-in-drop/text/0000-panic-in-drop.md) [FCP comment](https://github.com/rust-lang/rfcs/pull/3288#issuecomment-2028021992)",
  "title": "Code bloat caused by lack of nounwind attr on `drop_in_place`"
}