> Check out V-lang ... it has the details.

Does it? From its docs [0]:

> There are 4 ways to manage memory in V.

> The default is a minimal and a well performing tracing GC.

> The second way is autofree, it can be enabled with -autofree. It takes care of most objects (~90-100%): the compiler inserts necessary free calls automatically during compilation. Remaining small percentage of objects is freed via GC. The developer doesn't need to change anything in their code. "It just works", like in Python, Go, or Java, except there's no heavy GC tracing everything or expensive RC for each object.

> For developers willing to have more low-level control, memory can be managed manually with -gc none.

> Arena allocation is available via a -prealloc flag. Note: currently this mode is only suitable to speed up short lived, single-threaded, batch-like programs (like compilers).

So you have 1) a GC, 2) a GC with escape analysis (WIP), 3) manual memory management, or 4) ...Not sure? Wasn't able to easily find examples of how to use it. There's what appears to be its implementation [1], but since I'm not particularly familiar with V I don't feel particularly comfortable drawing conclusions from a brief glance through it.

In any case, none of those stand out as "memory safety without GC" to me.

[0]: https://docs.vlang.io/memory-management.html

[1]: https://github.com/vlang/v/blob/master/vlib/builtin/prealloc...

Oh, it's known. It just has an incredibly negative reputation on this site.