5 ms·
It's a common misconception that Haskell is slow to compile but not really true, see for example: http://www.shimweasel.com/2016/10/24/fast-tests-and-static-lan
by dkubb 10y ago
It's a common misconception that Haskell is slow to compile but not really true, see for example: http://www.shimweasel.com/2016/10/24/fast-tests-and-static-languages http://www.shimweasel.com/2016/10/24/fast-tests-and-static-l...
- mahyarm 10y agoThat feels like a limited optimization in the context of practical development.
- Athas 10y agoI guess it depends on your expectations. I'm working on a ~38000 SLOC Haskell program (an optimising compiler: http://futhark-lang.org http://futhark-lang.org), and with GHC 8.0.1, a full build takes about 7 minutes. I can cut off a minute or two by passing `--fast` to Stack. However, even small incremental builds take a significant amount of time due to linking, which is what annoys me the most. It's still far from making me disavow Haskell, but it's definitely not among the fastest-compilable languages. This program is also too big to load in GHCi, at least on my laptop with 8GiB of memory.
- mahyarm 10y agoThat's pretty uncanny, swift has a fairly sloc to time ratio too. The memory usage although is significantly less.
- mbrock 10y agoNo, it's a very common issue brought up within the community that GHC takes a lot of time and memory. That blog post just says that interpreting Haskell can be faster than compiling. I worked with Haskell professionally on a pretty large codebase. It was split up into many separate libraries and binaries. There were a lot of coffee breaks when recompiling. https://www.reddit.com/r/haskell/comments/45q90s/is_anything_being_done_to_remedy_the_soul/ https://www.reddit.com/r/haskell/comments/45q90s/is_anything...