On: The V Programming Language 0.4

[agumonkey]

I stopped looking long ago but to my limited understanding, when V says it does X in 1s, it means they delegated the job to gcc faster than others doing the whole work.

Either that or V author is up for a few ACM turing awards.

[delian66 → agumonkey]

The main claim, about V doing something in 1s, is about V compiling itself from source, on a modestly modern machine.

That is mainly because of how it is organized. tcc also compiles itself fast, because of how it works, and how it is organised.

That other compilers, like rustc, gcc or clang can not do it, because they have other priorities/tradeoffs, is their problem.

[agumonkey → delian66]

Each line is a different compiler building itself ?

[delian66 → agumonkey]

Sorry, I do not understand.

Each line of what?

[agumonkey → delian66]

In the benchmark listed on their website

are they comparing how long it takes for each platform P to compile v sources or P sources ?

[delian66 → agumonkey]

If you mean the table under "For comparison, space and time required to build each compiler", I think, that it is about what each compiler took in time and disk space to compile itself, on the same hardware, so it is about P compiling P sources.

V can not compile C or Go, Go can not compile C, and C compilers can not compile V or Go, so it can not be otherwise.

[amedvednikov → agumonkey]

You'd be surprised how much can be optimized even when using the same C compiler.

No header files hell for example.