Steven Schveighoffer wrote:
Just goes to show how useful a profiler is.

Yes, I'm glad you pushed me to do it.  Looking forward to the fix.

The two secrets to writing fast code are:

1. using a profiler
2. looking at the assembler output of the compiler

In my experience, programmers will go to astonishing lengths to avoid doing those two, and will correspondingly expend hundreds of hours "optimizing" and getting perplexing results.

Reply via email to