How safe is V at this point in time?

[codemanticism]

I wanted something as safe as Rust, but simpler to use. It's so complicated to create a global vector variable in Rust. So much boilerplate for something that I think should be made simpler. I don't using global variables is that bad. It's like it wants to hide details of how it works (like there being a String type in addition to a Vec type) from the user. It feels so overtly complex. A suggestion: for a reference that points to a character, there could be one component which is a pointer and another that is an index. I want to be able to do something like ((char_var >= '0') && (char_var <= '9')) in Rust more easily. I know there is a way to do that in the Rust standard library, but the C way is a lot more fun!

I think there could be a mode to use the borrow checker system of Rust, but in a simpler programming language, for multi-threaded code.
I think this programming language could have potential.

[Avey777]

This is a good idea and also the reason why many people come to V.
They were all attracted by Autofree.
But in reality, V does not have a borrow checker similar to Rust, which is very different

[medvednikov]

V will have both working autofree and ownership after the SSA backend is released.

Both of these memory management approaches will be optional.

GC will stay the default. -prealloc and manual will be an option as well.

[codemanticism]

What about undefined behaviour and type safety?