K-Nucleotide is currently the worst performing Haskell/ghc entry, by a good margin (16 times slower than the leader, vs. 6 times for the next worst). Several of the leading entries for multi-core k-nucleotide explicitly manipulate threads, while the Haskell/ghc entries do not. Is this a case of no one's gotten around to doing this, or is there another reason?
- No one's gotten around to it. Please enter a submission!