I don't have a good idea about what could break, but who knows what we'll find. 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.
On Wed, Jun 5, 2013 at 9:03 AM, Stephen Haberman <[email protected]>wrote: > Hey, > > So, there is a CL out there that I have kinda/sorta been shepherding > along to add support to GWT-RPC for final fields. > > The current CL is kinda complicated right now, because we have at least > two flags about whether to turn final-fields on/off and also whether to > warn about it when it is off. > > Seems like things would just be a lot simpler if we could say, screw > it, final fields are always serialized. No options, no warnings. It > just works. > > If we were building GWT-RPC from scratch, this is how it would work. > > However, previously in the "we can never break anything ever"-era of > GWT, this was deemed a breaking change and so not allowed. > > Given we seem to have lightened up on that, I'd like to re-ask, how > about for GWT 2.6, final fields are always serialized, no options, no > warnings, it just works? > > Any -1s? Otherwise I'll assume it's okay and move the CL over to Gerrit > and simplify it. > > - 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. > > > -- 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.
