Added a Step extension to allow a step to specify its parent

[adamtegen]

Also updated the minithreaded console example to show how to consume it.

This allowed the sub-timings to show under their correct parent.

[yellis]

What is the use case for this?

[adamtegen]

This aids in multi-threaded scenarios. It "fixes" the multi-threaded console example

[yellis]

Ok.

Can you please remove the changes to the Step and StepImpl function return types (and rebase so that it doesnt show in the PR history)? We don't want to change these as part of the PR.

[adamtegen]

The change on those return types was necessary because I needed to pass the Step into the SubStep function.

[yellis]

@NickCraver @dixon - what do you guys think about changing the return type of Step and StemImpl from IDisposable to Timing? Timing is the only type returned by these functions and it implements IDisposable, so in theory even though this is an API change, it wont break anyone's code.

[dixon]

I'll look at this PR this weekend.

[yellis]

@dixon you get a chance to check this out yet?

[NickCraver]

I agree with the problem here, but not necessarily the solution. A better option is that multi-threaded access just works, which is a much harder problem, but a better overall goal of solving. I'm taking a look at that next in v4 - working on async now.

I don't disagree with the timing steps returning Timing though (for general use), I'll make that change in the current v4 tree.