I know the answer is that it doesn't support this, but here's what I'm
wanting to set up to give a clearer view.
Suppose you have a set of nested messages that represent the application
state of an entire application, in this case a game and its entities and
various other stuff. Here's a trimme
On Jul 18, 2012, at 16:14 , Jeremy wrote:
> I understand, but if one wants to keep a large persistent message allocated
> and walk over it frequently, there is a price to pay on cache misses that can
> be significant.
I guess you are wishing that the memory layout was completely contiguous? Eg.
I understand, but if one wants to keep a large persistent message allocated
and walk over it frequently, there is a price to pay on cache misses that
can be significant.
In my situation I am maintaining a large persistent instance of a large
message type that I used as a cached data set to compare
On Jul 17, 2012, at 2:33 , Jeremy Swigart wrote:
> Is there a way to tell the proto compiler to generate message definitions for
> which the message fields are statically defined rather than each individual
> field allocated with dynamic memory? Obviously the repeater fields couldn't
> be fully
Is there a way to tell the proto compiler to generate message definitions
for which the message fields are statically defined rather than each
individual field allocated with dynamic memory? Obviously the repeater
fields couldn't be fully statically allocated(unless you could provide the
compil
