[SOLVED] On hiatus until (#113)

[oscbyspro]

I see no point in it - if I can't measure it. I'll work on other things until the performance profiling issue (#113) is solved. In particular, I need to know if pointer-based things are worthwhile. At some point, I'll have real-world use cases to rely on, but I'm not there yet.

[oscbyspro]

So, after seven eternities, I found the xctestplan option that matters:

Does anyone know what it does? Leaving it switched on ruins performance.

[oscbyspro]

I found this comment from  at developer.apple.com:

Note: Code coverage data collection incurs a performance penalty. Whether the penalty is significant or not, it should affect execution of the code in a linear fashion so performance results remain comparable from test run to test run when it is enabled. However, you should consider whether to have code coverage enabled when you are critically evaluating the performance of routines in your tests.

[oscbyspro]

Hm, the mystery is solved. I find it strange, however, that it was enabled by default. I've not had that problem before.