https://codereview.chromium.org/11358234/diff/1/src/elements.cc
File src/elements.cc (right):
https://codereview.chromium.org/11358234/diff/1/src/elements.cc#newco...
src/elements.cc:1551: return
AccessorPair::cast(backing_store->ValueAt(entry));
On 2012/11/14 17:30:39, Michael Starzinger wrote:
> This could potentially also be a Foreign callback or a AccessorInfo
callback. I
> am unsure if that ever happens in any of our embedders, so we could
just add a
> CHECK (on top of the implicit assertion) here that the value we get
out actually
> is a AccessorPair. WDYT?
The Foreign case is completely under our control and (very probably)
doesn't matter here, but the unhandled AccessorInfo case really makes me
nervous: If I understand things correctly, this would change our
external API with unknown consequences. I would very much prefer
avoiding this. If there is really, really no way around this, the
restriction (which one exactly?) should be documented in a very visible
way in our external header.
https://codereview.chromium.org/11358234/