3 ms·

Not 3 years ago.

• amedvednikov 3y ago
  Here's the version of the website 3 years ago: https://web.archive.org/web/20200629153446/https://vlang.io/ 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/ 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.
  • pca006132 3y ago
    https://web.archive.org/web/20200703221450/https://github.com/vlang/v/blob/master/doc/docs.md#memory-management https://web.archive.org/web/20200703221450/https://github.co... > 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.
    • amedvednikov 3y ago
      Yeah, this docs section was not synchronized with the landing page, and had bad wording. It says "work in progress", meaning that's something that's planned/being investigated. This was later worded better. But I agree, the docs should have never had such wording.
    • Tozen 3y ago
      Plus we are talking about a free open-source project, that's more of a grassroots effort, that didn't start as a corporate plan and creation. There are others contributing and writing documentation (and they aren't all English experts). Mistakes will happen and changes are allowed (many for the good). The language is not 1.0 yet, so should be allowed and will evolve/change over time (as other languages before it). People are also free to join the project or directly make helpful suggestions. That's part of the point of open-source.