Exploring Time-Space trade-offs for "synchronized" in Lilliput

[Roman Kennke]

Hi Gil,

> Roman, FWIW, in Zing (now called Prime) we use a similar optional hash-code word, but we place the hashcode in a pre-header word, rather than with an appended word. It fits in basically the same place (in a gap between objects, and can occupy an alignment gap if one exists), but is easier/faster to address. Putting it before the header eliminates the need to know the object size to get to the hashcode.

Indeed! This is a good suggestion! But doesn't this make size-based 
heap-parsing a bit more complicated? Given an object O in heap, how to 
find the next object after O?

Cheers,
Roman