Alex, all of these are still open right not and are not fixed:

- "No mut m := x mutability check" https://github.com/vlang/v/issues/14803

- "closure capture names are not checked for uniqueness with the closure parameter names" https://github.com/vlang/v/issues/14787

- "segfault in auto string method generated for []&int{len:1} (does not check for 0 pointers)" https://github.com/vlang/v/issues/14786

> using -prod for measuring compiler speed

My article does not do that. I included all the steps used and the 1,000,000 line tests use tcc and not -prod.

> And nonsense like setting array length on creation is a terrible idea. Go with its `make([]int, 5)` must be a terrible scam language as well.

V allows the user to override length field which is used in bounds-checking with no validation. That's the problem.

Please stop lying and just be honest about the state of V.

Given the behavior of you, Tozen and ylluminate on this thread, I have zero interest in interacting with the V "community" again.