2 ms·
The data was incorrect due to an oversight on my part (the Docker image I had used compiled GCC with internal assertions enabled). Including <print> is still v
by SuperV1234 7mo ago
The data was incorrect due to an oversight on my part (the Docker image I had used compiled GCC with internal assertions enabled).
Including <print> is still very heavy, but not as bad as before (from ~840ms to ~508ms)