On Tue, Nov 11, 2008 at 10:51 AM, Isaac Truett <[EMAIL PROTECTED]> wrote:
> > > I'm curious what things you're referring to here. Generally, I think > we're > > pretty open to more checks in hosted mode. As an example, hosted mode > always > > runs with assertions enabled. > > More assertions are exactly what I've been hoping for. The one case > that's stuck with me was issue 2365. As I understand it, those > assertions (and the check method, if only called in assertions) will > all be compiled away, so there's no size or performance penalty in web > mode. That's exactly right. And as we add new library classes, I anticipate we'll be doing a lot more assertion checking versus if/then/throw type tests. This is one area where I honestly believe the traditional Java patterns are just plain wrong: coding that's far too defensive. --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
