Right now, Mutex will assert if you assign it to an object with a monitor. Or it would with a non-release build. That's the only entirely safe thing to do.
Sent from my iPhone On Jan 7, 2012, at 9:27 AM, "Steven Schveighoffer" <schvei...@yahoo.com> wrote: > On Sat, 07 Jan 2012 11:08:51 -0500, Sean Kelly <s...@invisibleduck.org> wrote: > >> There's still a race condition between unlocking the monitor and freeing the >> memory. > > Wouldn't that result in a segfault or other error? How is that worse than > the current state of affairs? > > -Steve
