std.experimental.logger formal review round 3

[Robert burner Schadek via Digitalmars-d]

On Friday, 14 November 2014 at 21:43:53 UTC, David Nadlinger 
wrote:
>
> Except that they can't actually get rid of all the overhead 
> involved, as the locking is hard-coded into the Logger 
> base-class. Granted, acquiring an uncontended lock isn't 
> terribly expensive, but it's still a noticeable overhead if you 
> are just logging to a thread-local buffer otherwise.
>
> David

You can always roll your own non locking Logger, but the default 
should be thread-safe.