It is currently inconsistent, it is not enforced, most of GWT contributions are coming from Googlers who are not aware that GWT has different rules than all other Google3 code. Moving code from Google3 to GWT requires re-sorting. If you change the name of a function, you need to move the code to a new random location and on the review you can't see what really changed in the function or even if it has changed. I don't care much about internal stuff much but seeing an API in alphabetical order is as good as any other random order for the end users of the SDK. These are the similar reasons why none of other high profile libs (Guava, Guice, Dagger and JDK itself) enforce such rules.
On Thu, May 30, 2013 at 7:42 PM, John A. Tamplin <[email protected]> wrote: > On Thu, May 30, 2013 at 10:22 PM, Goktug Gokdogan <[email protected]>wrote: > >> At the end I guess this comes to personal preferences. >> If you personally prefer the static/non-static + alphabetical ordering, >> IDE can show it to you with a simple keystroke (Ctrl+O in Eclipse) but >> it can't do the reverse. >> > > So what is the rationale behind this proposal? GWT has operated the way > it is for many years. What problems has it caused? > > Are we no longer running ant checkstyle in the submit queue? > > -- > John A. Tamplin > > -- > 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.
