On 8/9/2015 2:25 AM, Iain Buclaw via Digitalmars-d wrote:
Now we have the testsuite, which seems to be a good enough gauge for finding problems. However if there's been a change (eg: refactor) between what codegen is lowered in the frontend vs. glue, then it becomes a commit hunt trawling through thousands of changes to work out which one is relevant to the new wrong-code-on-previously-working test. One day turns into a week, turns into a month, turns into half a year.
Would git bisect help with that?
