Hacker News Reader

I guess both Java and OCaml will see that the object can be generated on the stack which makes it much faster.

By using malloc in the C implementation, you force it to be on the heap.

Actually, OCaml never generates objects like this on the stack - value creation is always taken literally. The OCaml compiler is really allocating all those records. It's just that their lifetime is almost zero, so the cost to clean them up is zero (as none get promoted from the minor heap to the major heap). And the cost to create them is almost zero, just a += and a compare.

Ah, interesting. Does it also have a GC or some own custom allocation implementation?

Because if it really would use something like malloc, I don't really see how it should be faster than the C version.

Reply on news.ycombinator.com