“V compiles between ≈80k (C backend) and ≈1.2 million (x64 backend) lines of code per second per CPU core.” hmmm
https://vlang.io/
(Besides the language look like an interesting functional-ish variant of Go.)
@civodul if it compiles fast then it doesn’t do much useful stuff.
@fudgel You’re right of course, though V (or Go) aren’t as low-level as C either, so I do think it’s quite an achievement.
@civodul keeping compilation times short and monitoring them constantly https://fast.vlang.io/ is an engineering achievement (which Guix/Guile could copycat too).
At the same time speed is not surprising if we don’t handle edge cases yet https://github.com/vlang/v/issues
I *assume* V is relatively fast because it’s young, optimized for it and doesn’t perform a rigorous compilation yet.
@mandraker it’s a fundamental trade‑off— useful transformations aka more work require more time. If a compiler is fast it doesn’t do anything fancy so a programmer needs to make transformations by hand.
That’s why assembler compiles fast but high level langs slow.
If the compiler doesn’t do the job then the programmer must do the job (but slower and (almost always) worse).
@civodul