This was later worded better. But I agree, the docs should have never had such wording.
1,578 karma · joined November 15, 2016
This was later worded better. But I agree, the docs should have never had such wording.
https://web.archive.org/web/20200629153446/https://vlang.io/
Can you point to that claim?
Here's 4 years ago:
https://web.archive.org/web/20190828170427/https://vlang.io/
> V manages memory at compilation time (like Rust). Right now only basic cases are handled. For others, manual memory management is required for now.
This is very clearly explained on the website:
Code after that won't run at all.
I did an early release of the Patreon-only compiler without sources, and that was a mistake.
Check out vtl:
From the people at Discord:
> I run the infrastructure department at Discord which includes our anti-spam engineering team -- Just want to +1 what you're saying and confirm that we are never trying to ban third party clients (that aren't self-bots). Honestly, it would be a waste of our time and basically do nothing good for Discord.
No plans to support C compilation for now, translation works well enough.
https://www.youtube.com/watch?v=pvP6wmcl_Sc
> they expect V to compile itself in less than a second for the general case (not just one very specific case).
What on earth are you talking about? There's no specific case. Check the video. Try it yourself. Have you actually tried it?
Can you list the inaccurate claims here please and in progress features that are not clear to the user?
> until V's autofree engine is production ready.
This is false.
> Everyone wants you and V to succeed
The same people who write articles about V and say V should die?
One and only time a github comment was removed was before the open source release and I just started this new job of an open source maintainer.
Actually, sorry, I did remove one issue recently. It said "Delete this project, it's a joke".
It needs to be inited recursively with
app := App { gg: &gg.Context { ... app } }
And that doesn't work yet. It used to work in the initial V, but not right now.
It'll be fixed in 0.4.
As long as you use the same data structures and algos, you'll get the same perf.
There's stuff like bounds checking, but it can be disabled, and it adds like 5%.
The 200x compile speed up referred to C++ compilers, this was vague and hard to measure, since the languages are so different, and was removed.
The code may not have been perfect at the time of the 0.0.1 release, but it worked. V could compile itself.
Now it's much better and more organized.