On Tue, Jun 16, 2009 at 6:29 PM, Scott Blum wrote:
> Instant hosted mode should really change the game, right? We will no
> longer be speculatively compiling anything for TypeOracle since we'll be
> using class files that should already exist.
The problem is that if there is no class file, we
That would be marvelous. I hadn't thought through the implications of IHM,
but it seems like it might solve the problem.
What about types that aren't IHM compatible, such as those containing JSNI?
Could those still cause spurious errors?
On Tue, Jun 16, 2009 at 6:29 PM, Scott Blum wrote:
> Insta
Instant hosted mode should really change the game, right? We will no longer
be speculatively compiling anything for TypeOracle since we'll be using
class files that should already exist.
On Mon, Jun 15, 2009 at 11:21 PM, John Tamplin wrote:
> On Mon, Jun 15, 2009 at 11:11 PM, Bruce Johnson wro
+1 from me; I did a similar thing in STOB with regard to non-serializable
types.
I also think---though I don't have data to prove---that we often get spam
from classes that happen to be on the classpath, but could be provably
*not* reachable
(even by things like RPC polymorphism), for example from
On Mon, Jun 15, 2009 at 11:11 PM, Bruce Johnson wrote:
> We've known for a while that the GWT compiler is spammy, even at default
> log levels. There is a reason for this behavior, believe it or not:
> TypeOracle's JClassType#getSubtypes() call. Because generators can ask for
> the subtypes of an
