Is V memory management is ready or under development ?
I also want to know
Alex is working hard on memory management so the status is WIP.
V will use a combination of approaches by Rust, Nim, Lobster, Swift, C++ and main coder’s ideas.
Dec 22 10:50
I spent the past month learning Rust. I liked it. I accepted the programmer needed to be aware of the data lifetimes and the ownership rules, and sometimes write explicit code about them, as a necessity to achieve memory safety.
Yesterday I discovered V. I understood it intends to deliver Rust's memory safety and performance while staying closer to Go's simplicity and got very e
xcited! I read the whole introduction to the language in a bit more than an hour, and I found it enjoyable.
But I wonder how V will know when to "autofree" and when to use a reference-counting?
Can someone point me to any literature explaining the ideas behind its memory management strategies?
Log in via GitHub to comment
, open-source blogging/forum software written in V