Any "safe" subset of C++ will have to ban non-static methods, because "this" is an unsafe pointer.
@pcwalton I think a safe subset of C++ would "only" have to ensure that "this" is always safe to use in the contexts where it is used.
-
-
@BRIAN_____ I don't think there's any way to do that without a lifetime system. -
@pcwalton@BRIAN_____ swizzle to safely-no-op-and-error invalid object vtable after destruction? -
@shaver@pcwalton@BRIAN_____ And prevent malloc from reusing that memory until when? -
@jruderman@pcwalton@BRIAN_____ each this-with-vtable? dunno, it’s small, until the next full heap scan probably fine -
@shaver@jruderman@brian_____ Full heap scan probably requires stopping all threads. Global concurrent GC.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.