jat at google.com
Fri May 27 14:35:44 PDT 2011
On Fri, May 27, 2011 at 4:43 PM, Peter Michaux <petermichaux at gmail.com>wrote:
> Yes but I was thinking of the use of guards as a debugging/development
> tool. During development you can verify that foo is never called with
> bad values. Then during production, those checks do not need to be
> performed. By removing the debugging checks for production, this would
> save wire and execution time.
Sure, until a user typed in a value you never tried during development. You
can either rely on these for validating arguments, in which case they have
to stay, or you can't, in which case you can treat them like asserts.
John A. Tamplin
Software Engineer (GWT), Google
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss