3 ms·
Not saying it's not worth it, just, it's strange to put them in the same sentence when one is what makes the difference between usable and completely unusable.
by moonchild 3y ago
Not saying it's not worth it, just, it's strange to put them in the same sentence when one is what makes the difference between usable and completely unusable. I lived with 20-60s dirty build times for 1-line changes at symmetry, solely because of redundant compile-time recomputation—I wouldn't wish that on anybody. 10x would have been on the upper edge of tolerable, but you certainly won't get 10x for 'cheap'—and even so, latency should rightfully be measured in the milliseconds, not seconds. (~10x, incidentally, is quoted as an upper bound for newctfe here https://forum.dlang.org/post/qxiggjwhvadbpdfkidvu@forum.dlang.org https://forum.dlang.org/post/qxiggjwhvadbpdfkidvu@forum.dlan..., had it ever materialised.)
- mhh__ 3y agonewCTFE was actually hitting 50x on some things I benchmarked — locality again, to a good approximation. And my initial post did mention doing too much work in the first place.