Any "safe" subset of C++ will have to ban non-static methods, because "this" is an unsafe pointer.
-
-
Replying to @BRIAN_____
@BRIAN_____ I don't think there's any way to do that without a lifetime system.2 replies 0 retweets 0 likes -
Replying to @pcwalton
@pcwalton@BRIAN_____ swizzle to safely-no-op-and-error invalid object vtable after destruction?1 reply 0 retweets 0 likes -
Replying to @shaver
@shaver@pcwalton@BRIAN_____ And prevent malloc from reusing that memory until when?1 reply 0 retweets 0 likes -
Replying to @jruderman
@jruderman@pcwalton@BRIAN_____ each this-with-vtable? dunno, it’s small, until the next full heap scan probably fine1 reply 0 retweets 0 likes
Replying to @shaver
@shaver @jruderman @brian_____ Full heap scan probably requires stopping all threads. Global concurrent GC.
12:33 PM - 6 Oct 2013
0 replies
0 retweets
0 likes
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.