Christian Tietze

Inside of an actor, we can't assume `deinit` is isolated. If anything, we ought to assume the opposite.

Since there's no easy way to express "release all owned resources", the actual change I'm being nudged towards is: express ONLY resource ownership with a new type. There, you can use deinit.

This is #RAII from C++, but in Swift.

Sep 3, 2025 at 2:15pmWeb
Show threadPyry JahkolaSep 3, 2025
@ctietze For RAII in Swift, maybe also make the types `~Copyable`… like you'd do in C++ too!
Show threadChristian TietzeSep 3, 2025
@pyrtsa oooh that's a cool idea, thank you
Show threadChristian TietzeSep 3, 2025
@pyrtsa wait a second, classes cannot be non-copyable :)
Show threadPyry JahkolaSep 3, 2025
@ctietze But noncopyable structs have their deinits too!
Show threadMatt MassicotteSep 3, 2025
@ctietze I think you can use 6.1’s insolated deinit here. An assumeIsolated is not safe.