2 ms·
Hmm interesting. The first thing they mention is GC. IMO that's very solvable with manual intervention, and probably not too hard to solve with tooling. A call
by MichaelGG 13y ago
Hmm interesting. The first thing they mention is GC. IMO that's very solvable with manual intervention, and probably not too hard to solve with tooling. A call a simple as String.Split can require allocating multiple objects on the heap just to make the call. (An array to string objects.) There's no reason this couldn't be stack-allocated. Similarly, there's probably lots of code that'd benefit from a pool allocation, like say, processing an HTTP request, where GC can be done just by freeing the pool.