nimcr again:
'./count.nim' ran
5.94 ± 0.74 times faster than 'python3 count.py'
8.99 ± 0.99 times faster than 'ruby count.rb'
147.58 ± 19.96 times faster than 'bash count.bash'
Run
That's from:
#! /usr/bin/env nimcr
#nimcr-args c --threads:off --cc=tcc --passl:"-ldl -lm"
var c = 0
for i in 0 ..< 1_000_000:
c += 1
echo c
Run
IC's not going to make gcc compile a program like this any faster than tcc
does, but if you're writing scripts, the point of nimcr is to take the
compilation time out of the practical timing. You only compile when the program
changes. This is 'unfair' as a benchmark, but it's unfairness to the advantage
of the programmer - to have a convenient language (Nim), and to have scripts,
and to also have good runtime performance.
