On Tue, Jun 9, 2009 at 12:11 AM, Jon Skeet sk...@pobox.com wrote:
On Jun 9, 1:42 am, Kenton Varda ken...@google.com wrote:
In the next version there will be a third option: LITE_RUNTIME. This
variant is like optimizing for speed but will generate code that only
depends on a lighter
On Jun 9, 8:31 pm, Kenton Varda ken...@google.com wrote:
Is the plan that the reflection parts of the API will just throw
exceptions, or will there be non-reflection interfaces which are
implemented by these generated classes?
There will be a new interface called MessageLite which is a
Hi,
Can anyone tell me what are the caveats of using the option
optimize_for = SPEED; during code generation?
The documentation says it can improve parsing and serialization. But
what are the cons of using this?
Thanks,
Wayne
--~--~-~--~~~---~--~~
You received
Hi,
On Mon, Jun 8, 2009 at 2:03 PM, wayne.mene...@gmail.com wrote:
Hi,
Can anyone tell me what are the caveats of using the option
optimize_for = SPEED; during code generation?
The documentation says it can improve parsing and serialization. But
what are the cons of using this?
Mostly
