V claims to take care of most objects (~90-100%) and uses GC for the stuff it can't figure out during compilation.
This is very clearly explained on the website:
This is very clearly explained on the website:
https://web.archive.org/web/20200629153446/https://vlang.io/
Can you point to that claim?
Here's 4 years ago:
https://web.archive.org/web/20190828170427/https://vlang.io/
> V manages memory at compilation time (like Rust). Right now only basic cases are handled. For others, manual memory management is required for now.
> V doesn't use garbage collection or reference counting. The compiler cleans everything up during compilation. If your V program compiles, it's guaranteed that it's going to be leak free.
This was later worded better. But I agree, the docs should have never had such wording.
People are also free to join the project or directly make helpful suggestions. That's part of the point of open-source.