Added disabled IE10 permutation

 * Mostly just rebinding to old IE9 implementations
 * Rebinding to newer implementation with follow up patches

issue 8063

Change-Id: Iba0cec6e33ffd3fefa69c3c760868beb00d42076
Enable IE10 permutation

fixes issue 8063

Change-Id: Ib92feb14ab2658daf5d8eb466ef359b67ffc9864
Disable IE6 permutation

Change-Id: I28a378c7693c7dd1497b6ef01b14efbed9a5d086
Small refactoring in CodeSplitter.

Moved LivenessPredicate interface and some implementors to top level.

Change-Id: I76aea558246bc478e361e9191c288cef9d70a733
Removed README details about non-existant gwt-customchecks.jar

Change-Id: I269edf123244fbdf04ec7cd1988a546f97d4476d
Discussion: https://groups.google.com/d/topic/google-web-toolkit-contributors/s1-kIzWE9-M/discussion
Related: https://gwt-review.googlesource.com/#/c/1051/
Refactors TypeOracleBuilder/TypeOracleMediator

Combines TypeOracleMediator and TypeOracleMediatorFromSource since they
both were claiming to operate on CompilationUnits and no non-test code
existed that depended on the difference between them.

Replaced "Builder" and "Mediator" verbiage with the more accurate term
"Updater".

This patch is mostly just a cleanup and clarification. The only
behavior change is that where previously TypeOracleBuilder instantiated
a TypeOracle instance during its initialization, now an instance is
passed in via constructor.

Change-Id: I8c9078e651a3eab03730ad36c5db0c9dd6499216
Review-Link: https://gwt-review.googlesource.com/#/c/5038/
Small refactor to CompoundAssignmentNormalizer.

CompoundAssignmentNormalizer allows subclasses to choose different
strategies for creating locals.

By default CompoundAssignmentNormalizer creates uninitialized locals
all with the same name; assuming that equal names do not imply same
variable.

Subclasses might decide to create unique names or initialized
locals instead to serve different scenarios.

Change-Id: Ia19e19f154e6f2490af6b8729e71e73f6a6acd24
Adds methods to StubScheduler to execute the recorded commands somewhat similarly to the real SchedulerImpl.

Change-Id: I863c31c4a72a1a79064ad8a31e18c9efde5d63ef
Review-Link: https://gwt-review.googlesource.com/#/c/4540/
Change getSubRowElement's visibility to protected

Change-Id: Id3aa37d67b09b5048481d7ff10d38ff009c7ed4b
DateTest now passes in all timezones

Change-Id: If10e426aa2350883493e37e0f4ebe8cd75ae013c
Add "superdevmode" rule to Ant files generated by WebAppCreator

As a result, the sample apps that use Ant will have a "superdevmode"
rule.

Verified that it works with Hello. It currently doesn't work with
Showcase because ShowcaseGenerator assumes that it can read
Java source code using the classloader; we'll need a different API
for reading source from the GeneratorContext.

Change-Id: I059bf8eaffd0b28ebd0c34088edbed690b44b5a6
Refactor CssResourceGenerator to share code.

In the context of writing a generator for supporting Google closure
stylesheet, this little refactoring is needed in order to share some
code between the different generators.

The draft implementation of GssResourceGenerator :
https://github.com/jDramaix/gss.gwt/pull/1

Related thread on contributors group :
https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/e0qUfkqBSog

Change-Id: I1046d34dc92f2bd3baeb7d4852c146253f858e47
Refactor JForStatement construct.

The third part of a JForStatement can only be a list of expressions.
This patch changes its representation from a List<JExpressionStatement>
to a JExpression (which in some cases will be a JMultiExpression).

Some later passes, such as CompoundAssignmentNormalizer are simplified
as a result (in a following patch).

Change-Id: Ice90e323698ef5ec24ff744df04ee0c182d0e7e9
Enable Super Dev Mode for samples that use Ant

Also enables Super Dev Mode by default in Ant
projects created using webAppCreator.

Change-Id: Ia515696a420adbead2d9776330d430b4ab428c04
Revert "Rescue Arraytype from ArrayPrototypePatcher"

This reverts commit cc13d5d2c7055e93e53b1abd56b38241e85f90d2.

Change-Id: I8b9d517ce422a06879676962650cb19cf07d8913
Revert "Always include Array type in instantiated types"

This reverts commit 1c3e181002d05dbd9fa8af97079345307ba4c350.

Change-Id: I7cd12dee86b2145e6d88f409825fd9179e517f4d
Revert "Update Array class to be faster"

This reverts commit 68372eabcf0cbb24ee74f63a98b52a0eb7cffed7.

Change-Id: I3adc78fb2ec0f4f083ce98f3a867fe68452c02b9
Fix CompoundAssignmentNormalizer to create locals with declarations.

A previous patch removed the creation of declaration statement nodes
in the AST during temp local creation. The current JavaScript
generation approach does not rely on the existence of these
declaration statement nodes since it uses the function scope locals
list, but the nodes might be needed in the future.

So this patch is restoring them.

Change-Id: I9a4cf9b4dda02f05ad705f94df8bded24fa8519d
Supplies CompilerContext all over the call graph.

Separate compilation creates the need to have access to loaded
precompiled libraries, the current library builder, options
and the global unitCache all over the call graph. Rather than
add four new parameters to most of the call graph it was
decided to group them together and add just one new parameter
to most of the call graph (and in some places remove some now
redundant parameters).

Going further, existing compilation assumes that build,
source, and public resources should always be accessed out of
resource oracles attached to the module object. But with
separate compilation resource loading needs to be serviced
from a combination of the current module and precompiled
libraries. So the CompilerContext also serves as a consistent
place for compiler code to access resource oracles without
the accessing code having to know from whence those resources
originated.

The rest of the separate compilation work makes heavy use of
the CompilerContext and its presence throughout the call graph,
so while it's weird to be submitting a CL that introduces so
many temporarily unused function parameters its very useful in
that it opens up a lot of the remaining separate compilation
changes to be reviewed in small pieces.

To keep things sane the CompilerContext contents are treated as
read only except at the very top of the function call tree
(like the main function and tests).

Some alternative designs were considered but rejected for
various reasons:
 * dependency injection, would require a massive general refactoring
 * singletons, not thread safe
 * thread local variables, too magical and would lead to odd
   instance hand-offs between threads

That being said design feedback and counter suggestions are welcome.

Change-Id: I1c56dd7cd5d8b333f8ffac455be280a8718d8cd1
Review-Link: https://gwt-review.googlesource.com/#/c/5170/
Add DataGrid.setAlwaysShowScrollBars.

Change-Id: Ifa2c132b6ecfc723b647bef9cabce634b80d8dec