1. I suspect what's really slow here is Nim's IO or unzipping and this should definitely be looked into and fixed. 2. Well, yes, strutils is for quick & dirty hacking, not for "quick runtimes". And optimizing splits is easier said than done, effectively you need 2 different versions so that split continues to work at compile-time. And then it still adds maintainance costs. Plus in the end all you do is to make somebody's bugs run faster.
- Nim vs. Python & Groovy (string splitting): Why is str... markebbert
- Re: Nim vs. Python & Groovy (string splitting): W... Stefan_Salewski
- Re: Nim vs. Python & Groovy (string splitting... siloamx
- Re: Nim vs. Python & Groovy (string split... erikenglund
- Re: Nim vs. Python & Groovy (string s... Araq
- Re: Nim vs. Python & Groovy (str... siloamx
- Re: Nim vs. Python & Groovy ... cblake
- Re: Nim vs. Python & Gro... Araq
- Re: Nim vs. Python & Gro... cblake
- Re: Nim vs. Python & Gro... Araq
- Re: Nim vs. Python & Gro... cblake
- Re: Nim vs. Python & Gro... jlhouchin
- Re: Nim vs. Python & Gro... federico3
- Re: Nim vs. Python & Gro... jyapayne
- Re: Nim vs. Python & Gro... cblake
- Re: Nim vs. Python & Gro... kaushalmodi
- Re: Nim vs. Python & Gro... cblake
- Re: Nim vs. Python & Gro... zetashift
- Re: Nim vs. Python & Gro... cblake
- Re: Nim vs. Python & Gro... zulu
