Comparison of space and time required to build each compiler for system language
forum.devtalk.com
forum.devtalk.com
The developer doesn’t need to change anything in their code. “It just works”, like in Python, Go, or Java, except there’s no heavy GC tracing everything or expensive RC for each object.
How are cycles handled, especially if the code does not require any special handling? The documentations only says that this is still work in progress and currently a garbage collector is used by default.
For developers willing to have more low level control, autofree can be disabled with -manualfree, or by adding a [manualfree] on each function that wants manage its memory manually. (See attributes).
Note Autofree is still WIP. Until it stabilises and becomes the default, please avoid using it. Right now allocations are handled by a minimal and well performing GC until V's autofree engine is production ready.
As for V compiling itself, the times that I've read about anytime in the last couple of years, is around 0.3 to 0.4 or so.
[1] Ask HN: Why do you use Rust, when D is available?
If a person is that offended or disturbed that others like a different language, just leave it be, and go play with what you do like. Different people, like different languages, time to accept that.
My post might get downvoted into oblivion for daring to speak out about such bullying and odd behavior, but somebody has to speak out when such wrongs are being perpetrated.
wget http://download.savannah.gnu.org/releases/tinycc/tcc-0.9.27.tar.bz2
tar -xzf tcc-0.9.27.tar.bz2
cd tcc-0.9.27
./configure
time make
generates: ...
make 5.01s user 0.43s system 95% cpu 5.720 total
so I guess there are some fast c compilers too... git clone https://git.sr.ht/~mcf/cproc
cd cproc
git submodule init --update
time make qbe
time make
generates: make qbe 0.81s user 0.07s system 97% cpu 0.901 total
make 0.83s user 0.07s system 99% cpu 0.902 total