OT: std.logger was Re: std.experimental Timeline

Robert burner Schadek via Digitalmars-d digitalmars-d at puremagic.com
Tue Jan 5 08:44:25 PST 2016

On Tuesday, 5 January 2016 at 16:34:27 UTC, Dicebot wrote:
>> BTW, the default implementation is a direct result of the "by 
>> default multi-threading safe" requirement brought up multiple 
>> times during reviews.
> .. this remains a concern. I know that with some tweaks and lot 
> of custom overriding I can build logging system that works with 
> reusable buffers. However, it would be incompatible with any 3d 
> party logger which is defined in terms of `LogEntry` and that 
> kills the main benefit of having standard API in the first 
> place.
> I'd like (if it is even possible) to have a fast thread-safe 
> no-allocation logger with thread-local proxies as a default one 
> available because it is both very common demand from a logging 
> system and will influence how derived 3d-party loggers will be 
> designed.

If you could write this up as a callgraph with some (ascii) art 
showing thread boundaries, you would help me a lot understanding 
your requirement.

> But that can be a more problematic task because `const(char)[]` 
> ....
> original proposal and reading it in great details).
>> Anyway, if people have issues with std.(experimental.)logger, 
>> please write to the forum, bugzilla, github, or directly to me.
> As I have mentioned in the e-mail, I will do so as soon as I 
> will have any half-decent proposal and will be able to help :)

You don't need to do my work, it is nice of you to do that, but 
all I need is a problem description I can work with.

More information about the Digitalmars-d mailing list