While D is famously fast to compile in general, one sometimes runs into nasty slowdowns.
To help track this, it would be useful if makd could generate timings for different targets and output a summary. Ideally this would be output in a way that makes it possible to track stats over time, similar to coverage, so that we could observe outlier builds that may be associated with problematic code or compiler changes.
While D is famously fast to compile in general, one sometimes runs into nasty slowdowns.
To help track this, it would be useful if makd could generate timings for different targets and output a summary. Ideally this would be output in a way that makes it possible to track stats over time, similar to coverage, so that we could observe outlier builds that may be associated with problematic code or compiler changes.