3 ms·
how's the compile time with nim? go's compile time makes it almost as good as having a repl. i tried crystal a while ago and it has atrocious compile times.
by mlevental 9y ago
how's the compile time with nim? go's compile time makes it almost as good as having a repl. i tried crystal a while ago and it has atrocious compile times.
- dom96 9y agoThe compile times are on par with Go. The Nim compiler (written in Nim and containing ~100k LOC) compiles in under 10 seconds on my MacBook Pro, and this is from a cold cache. It's even faster when making changes as the C source files generated by Nim are cached.
- merb 9y agothe question how big are the compile times on a project in the size of kubernetes, i wouldn't call that "quick compile time". even the go part of it. I mean yes the use case for many people who use go have a fast compile time, but once it goes huge, the speedup isn't as big as on other languages.
- mlevental 9y agotangential question: are there still compiler bugs?
- dom96 9y agoOf course, all software has bugs :)
- wyager 9y agoThis is not true, and shouldn't be used as a lazy excuse to write bad software. There is absolutely software that is entirely free of bugs; it just takes formal methods to get there for software of any reasonable complexity.
- webkike 9y agoYou can never however guarantee that a program will run free of errors. Hardware is faulty and not always in ways that are human caused: en.m.wikipedia.org/wiki/ECC_memory
- dom96 9y agoSure there is. But in practice most compilers I know of contain multiple bugs. The main difference between the compilers is how many users these bugs affect.
- deleted 9y ago[deleted]