vlang uses Lobster's memory model, so the tradeoffs are: * It falls back on RC when it can't guarantee something's lifetime, so it still does some RC. * Can't

vlang uses Lobster's memory model, so the tradeoffs are: * It falls back on RC when it can't guarantee something's lifetime, so it still does some RC. * Can't store objects on the stack. (Lobster mitigates this with other aspects of their memory model, I'm not sure if vlang does) * Vulnerable to cycle leaks. IIUC vlang has no weak refs to break these cycles yet. * Space overhead per object to store the RC. Still, its nice to see more languages not using GC. Hopefully as Lobster innovates, vlang can adopt more of their techniques.