LogWriter synchronization problem

[Google Code Exporter]

In new 2.0 version, just as stated LogWriter is a channel, and a new go-routine 
is spawned to manage the printing.

But when a main program exited too quickly before that go-routine can finish 
processing the logs from channel, then these logs will be lost. Even 
logger.Close() won't resolve this.

Need some extra synchronization codes maybe, like embed a feedback channel 
inside the type LogWriter so logWriter.Close() can exam this channel and wait 
until all logs are printed.

Original issue reported on code.google.com by [e-mail] on 22 Sep 2011 at 1:57

[Google Code Exporter]

Is there any progress on this issue?  I'd love to use this code in production, 
but the possibility of messages getting lost on exit or in the event of an 
unforeseen panic is a big deal breaker.  This issue is over two years old.  
Should we be using another package now? 

Original comment by [e-mail] on 2 Feb 2014 at 9:49