On 05/17/2010 11:10 AM, Avi Kivity wrote:
Another way of looking at it: if the client sees { __class__: foo, f1: 10, f2: 9 }, it cannot derive any information from __class__ unless it was aware of foo beforehand. If that's the case, let's make it part of the schema so it is available at compile time instead of runtime.
Or both. That's similar to a non-object field's type being described both in the schema at during runtime. A static parser can verify __class__ matches the expectations, a dynamic parser can look up __class__ and call the appropriate constructor.
-- Do not meddle in the internals of kernels, for they are subtle and quick to panic.
