|
|
|
|
|
by amedvednikov
1463 days ago
|
|
Mostly all this post has is some type checker bugs that have already been fixed (of course the article will never be updated now that they're fixed) and using -prod for measuring compiler speed, when it's explicitly mentioned on the website it's for non optimized builds only. 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. If he had a good faith, he'd report these issues via GitHub, and they'd get fixed within a week. So, regarding your claim that I have "a habit of overpromising and even declaring things finished before even starting on them". Please, list them here. 1.2.3. Must be easy if there's a habit. |
|
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.