> I don't have a good idea about what could break I believe nothing would "break"--it's that final fields that were previously not going over the wire would now go over the wire.
So, I guess technically that is a change in semantics--so it wouldn't be like "oh, your GWT app fails to compile", more like "you were doing *what* with that field...that doesn't work anymore". Or we're exposing a value over the wire that previously the developer knowingly made final so that it would not (seems pretty odd though...). > I think we will at least want a flag to turn it on and > off. It might be temporary just to land the patch; not sure if it > should survive until the 2.6 release. Okay, well, technically a flag for that already exists in the patch--I suppose we could land it as is and then hope to maybe remove it by 2.6 or there after. I was just hoping to simplify it. I'll plan to move it over to gerrit then... - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
