• Bastiaan Veelo (11/11) Feb 29 2016 Is there a central place to document field testing of packages in
• Jesse Phillips (6/18) Mar 01 2016 My comment is that I've had a hard time replacing the shared

Bastiaan Veelo <Bastiaan Veelo.net> writes:

Is there a central place to document field testing of packages in 
std.experimental, to help determine when they are ready?

Pegged has recently started using std.experimental.logging for 
doing parse traces [1]. The only comment I have from this 
application is that maybe there should be a way to omit the time 
stamp decorations without creating a custom logger class [2].

Bastiaan.

[1] 
https://github.com/PhilippeSigaud/Pegged/wiki/Grammar-Debugging
[2] 
https://github.com/PhilippeSigaud/Pegged/blob/bc1679062d785ce9127070ed1c04bf2e1afaeaae/pegged/peg.d#L153

Jesse Phillips <Jesse.K.Phillips+D gmail.com> writes:

On Monday, 29 February 2016 at 09:49:23 UTC, Bastiaan Veelo wrote:
 Is there a central place to document field testing of packages 
 in std.experimental, to help determine when they are ready?

 Pegged has recently started using std.experimental.logging for 
 doing parse traces [1]. The only comment I have from this 
 application is that maybe there should be a way to omit the 
 time stamp decorations without creating a custom logger class 
 [2].

 Bastiaan.

 [1] 
 https://github.com/PhilippeSigaud/Pegged/wiki/Grammar-Debugging
 [2] 
 https://github.com/PhilippeSigaud/Pegged/blob/bc1679062d785ce9127070ed1c04bf2e1afaeaae/pegged/peg.d#L153

My comment is that I've had a hard time replacing the shared 
logger. When I swap it out none of my log() calls work, but it 
works as expected if I change them to sharedLog.log().

Since I haven't taken time to create a reduce test case I haven't 
filed a bug.