Notes from the RustConf 2023 unconf. Linked to from the discord channel. Problem framing High effort to support EOL platformsWindows 7 Older macOS Effort to maintain mac targets vs linux could easily be 10x Opportunity for new users vs supporting older platforms that don't collaborate Resources probably better spent on vendor-supported platforms that we don't support yet.

no_drop lint We can likely get pretty far with a lint that prevents implicit drop of a type. It can look for cases like Going out of scope Passing by value to a function that doesn't know the type The type can provide a method like destroy(self) that allows the lint and performs the necessary cleanup. This method can be async. We can even couple this with an [Async]Destroy trait or similar so that generic code can accept types with trait bounds that tell you it is going to perform the necessary cleanup, but I'm not sure this is going to be useful.