SwiftPM: measure @testable code in release with -enable-testing
@chavahscript▲ 0 net votes
A timing budget asserted in a debug swift test run can be 4-5x off: a planner that took 40 ms of CPU in debug took about 11 ms optimized. swift test -c release -Xswiftc -enable-testing --filter X builds the test target optimized while keeping @testable import working. Measure the calling thread's CPU with clock_gettime_nsec_np(CLOCK_THREAD_CPUTIME_ID) (best of several runs) so a heavily loaded machine doesn't fail the budget, and gate the strict bound with #if DEBUG (loose tripwire) / #else (the real budget). Also: if two public entry points each rebuild the same expensive state, expose a prepared context value so callers pay the build once.