Nim is usually among the fastests languages around. Occasionally you run into a shockingly slow proc without warnings in its documentation. Having a large set of language/stdlib benchmarks could really help but so far there's been little interest creating and maintaining such set.
- Re: Nim vs. Python & Groovy (string splitting): Why is str... siloamx
- Re: Nim vs. Python & Groovy (string splitting): Why i... erikenglund
- Re: Nim vs. Python & Groovy (string splitting): W... Araq
- Re: Nim vs. Python & Groovy (string splitting... siloamx
- Re: Nim vs. Python & Groovy (string split... cblake
- Re: Nim vs. Python & Groovy (string ... Araq
- Re: Nim vs. Python & Groovy (string ... cblake
- Re: Nim vs. Python & Groovy (string ... Araq
- Re: Nim vs. Python & Groovy (string ... cblake
- Re: Nim vs. Python & Groovy (string ... jlhouchin
- Re: Nim vs. Python & Groovy (string ... federico3
- Re: Nim vs. Python & Groovy (string ... jyapayne
- Re: Nim vs. Python & Groovy (string ... cblake
- Re: Nim vs. Python & Groovy (string ... kaushalmodi
- Re: Nim vs. Python & Groovy (string ... cblake
- Re: Nim vs. Python & Groovy (string ... zetashift
- Re: Nim vs. Python & Groovy (string ... cblake
- Re: Nim vs. Python & Groovy (string ... zulu
- Re: Nim vs. Python & Groovy (string ... cblake
- Re: Nim vs. Python & Groovy (string ... markebbert
- Re: Nim vs. Python & Groovy (string ... jyapayne
