← Back to context

Comment by bheadmaster

2 years ago

What about GC-less autofree?

I'm still waiting for that CS breakthrough to happen - Rust guys will be so mad they spent their time writing lifetime annotations for the borrow checker :)

You can look up vlang.io on web archive and see that it never said GC-less autofree. It actually explicitly said that RC/GC are used for stuff that can't be freed during compile time.

  • > Is there garbage collection?

    March 2019

    > No. V's memory management is similar to Rust but much easier to use. More information about it will be posted in the near future.

    May 2019

    > No. V manages memory at compilation time (like Rust). Right now only basic cases are handled. For others, manual memory management is required for now. The right approach to solve this will be figured out in the near future.

    April 2020

    > No. V manages memory at compilation, like Rust: vlang.io/docs#memory

    August 2023

    > You can look up vlang.io on web archive and see that it never said GC-less autofree

    • Nowhere in your quotes does it say GC-less autofree.

      "The right approach to solve this will be figured out in the near future."

      And it was figured out, and we now have what we have. It's described on the home page in detail. 4 ways to handle memory.

      Why another new account?

  • Here's a direct quote from the documentation [0] from 2021:

    > Most objects (~90-100%) are freed by V's autofree engine: the compiler inserts necessary free calls automatically during compilation. Remaining small percentage of objects is freed via reference counting.

    So most objects are freed by the autofree engine, and the rest are freed via reference counting. This implies that no objects are freed by the GC, which is exactly what I've said.

    Please stop gaslighting people.

    [0] https://web.archive.org/web/20210315092012/https://github.co...