Michael W Powell

@repi I'm sure it's for *REQUIRE* as well. I just called out *INFO* as a first observation. Point is, **thread-safety** is ***A MUST***.

@philsquared I'd say with the advent of *std::thread*, there really is no excuse for it to be a wish. In other words, that's not strong enough of a word, IMO.

@repi @philsquared Yes, I think we agree on the *what*. Now is a question of the *when*, which may necessarily be predicated on the *who*.

No idea; I've moved on to other non-C++ areas at the moment, so this is not on my radar screen apart from peripheral view.

TBH, a pub/sub pattern is going to guard its boundaries anyway. Probably internally, i.e. with a mutex.

Yes of course. The runtime and the scaffold being what it is. Of course, I am an OO guy, and I like the abstraction. From the consumer perspective, which is...

I might be missing a whole lot if I am reading the issues correctly. So, this needs ot be TS compiled for it to be available? Isn't it possible to...

Specifically, I need to persuade the SlowCheetah tasks to happen before the Nuget ones, I think. That would most likely capture the correctly transformed output.

@davilimap I think the issue is, I do not see any [nuget targets](https://github.com/Microsoft/slow-cheetah/blob/master/src/Microsoft.VisualStudio.SlowCheetah/Build/Microsoft.VisualStudio.SlowCheetah.targets) references there. I might half expect there to be ``BeforeTargets`` for instance. I'll have a look at...

I have not reviewed it closely yet, but here goes: [diagnostic-build-1.txt](https://github.com/Microsoft/slow-cheetah/files/2350313/diagnostic-build-1.txt)