Any "safe" subset of C++ will have to ban non-static methods, because "this" is an unsafe pointer.
@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? - 2 more replies
New conversation -
-
-
@pcwalton It wouldn’t necessarily have to be part of a *type* system though. Could use GC, refcounts, etc.— dynamic lifetime guarantee. -
@pcwalton Oh, you said “subset”, sorry - 2 more replies
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.