Comment #1 by timothee.cour2 — 2018-03-08T00:24:05Z
ping.
from previous posts above the OP it seems it gets a factor 4X slower.
here's the OP to make it easier:
```
On Wednesday, 10 January 2018 at 21:32:55 UTC, Nathan S. wrote:
> On my mac laptop running DMD 2.078.0, building and running the mir-algorithm unittests takes 8 seconds normally but takes ~3 minutes 49 seconds with dub options "releaseMode", "optimize", "inline", "noBoundsCheck".
When I remove the "inline" option the build + test time becomes <10 seconds. So the weirdly slow part is related to inlining.
```
and:
```
DMD 2.077.1 for linux32: 3 min 20 sec
DMD 2.077.1 for linux64: 3 min 16 sec
DMD 2.077.1 for mac64: 5 min 4 sec
DMD 2.078.0-rc.1 for linux32: 13 min 30 sec
DMD 2.078.0-rc.1 for linux64: 9 min 39 sec
DMD 2.078.0-rc.1 for mac64: 10 min 56 sec, then the job was aborted
```
Comment #2 by ilyayaroshenko — 2018-03-08T04:38:31Z
Mir Algorithm tests are a huge chunk of a super generic code. The same problem exists for a ultra Phobos-idiomatic code based on std.range and std.algorithm.
Comment #3 by robert.schadek — 2024-12-13T18:56:06Z