Add a native data property that replaces itself with a real data property

Add a native data property that replaces itself with a real data property

This is useful for things that don't ever change, but we don't want to
eagerly compute the result.

Doing this from the embedder is difficult, using DefineOwnProperty would
read the property to get the property descriptor, creating an endless
recursion.

R=verwaest@chromium.org,haraken@chromium.org
BUG=

Committed: https://crrev.com/f07421508221dfcca43a6c10ad8e9047f8f8fcdf
Cr-Commit-Position: refs/heads/master@{#40648}

[jochen (gone - plz use gerrit), 2016-10-27 11:01:58]

The CQ bit was checked by jochen@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-27 11:02:00]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[jochen (gone - plz use gerrit), 2016-10-27 11:02:21]

wdyt?

we could use this for the v8ConstructorMethodGetter in blink

[commit-bot: I haz the power, 2016-10-27 11:28:30]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-27 11:28:31]

Dry run: This issue passed the CQ dry run.

[Toon Verwaest, 2016-10-27 12:19:32]

Huh? That's the default setter behavior for special data properties?

[jochen (gone - plz use gerrit), 2016-10-27 12:39:35]

On 2016/10/27 at 12:19:32, verwaest wrote:
> Huh? That's the default setter behavior for special data properties?

only if you actually set it.

This patch makes the getter invoke the setter

[Toon Verwaest, 2016-10-28 14:05:21]

I would at least drop all of the accessor.cc changes. We have complete control
over those already; and we can support them directly if needed.

https://codereview.chromium.org/2449783006/diff/1/src/accessors.cc
File src/accessors.cc (right):

https://codereview.chromium.org/2449783006/diff/1/src/accessors.cc#newcode805
src/accessors.cc:805: &FunctionLengthGetter, nullptr, attributes, true);
This technically all works, but it won't give good perf / memory at all :)

[jochen (gone - plz use gerrit), 2016-10-28 14:12:28]

The CQ bit was checked by jochen@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-28 14:12:34]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[jochen (gone - plz use gerrit), 2016-10-28 14:13:04]

The CQ bit was checked by jochen@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-28 14:13:14]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Toon Verwaest, 2016-10-28 14:26:04]

lgtm; you'll need to investigate the impact for specific use-cases :)

[jochen (gone - plz use gerrit), 2016-10-28 14:36:17]

The CQ bit was unchecked by jochen@chromium.org

[jochen (gone - plz use gerrit), 2016-10-28 14:36:19]

The CQ bit was checked by jochen@chromium.org

[commit-bot: I haz the power, 2016-10-28 14:36:30]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-28 14:39:44]

Committed patchset #2 (id:20001)

[Benedikt Meurer, 2016-10-28 17:17:39]

I don't know how, but according to AWFY, --turbo --ignition-staging took a
serious hit with this CL, esp. NavierStokes? The default configuration doesn't
seem to be affected?

[jochen (gone - plz use gerrit), 2016-10-28 17:36:56]

On 2016/10/28 at 17:17:39, bmeurer wrote:
> I don't know how, but according to AWFY, --turbo --ignition-staging took a
serious hit with this CL, esp. NavierStokes? The default configuration doesn't
seem to be affected?

uhm. does this also show up on our bots? not sure how this would affect
anything..

[commit-bot: I haz the power, 2016-11-17 22:16:53]

Description was changed from

==========
Add a native data property that replaces itself with a real data property

This is useful for things that don't ever change, but we don't want to
eagerly compute the result.

Doing this from the embedder is difficult, using DefineOwnProperty would
read the property to get the property descriptor, creating an endless
recursion.

R=verwaest@chromium.org,haraken@chromium.org
BUG=
==========

to

==========
Add a native data property that replaces itself with a real data property

This is useful for things that don't ever change, but we don't want to
eagerly compute the result.

Doing this from the embedder is difficult, using DefineOwnProperty would
read the property to get the property descriptor, creating an endless
recursion.

R=verwaest@chromium.org,haraken@chromium.org
BUG=

Committed: https://crrev.com/f07421508221dfcca43a6c10ad8e9047f8f8fcdf
Cr-Commit-Position: refs/heads/master@{#40648}
==========

[commit-bot: I haz the power, 2016-11-17 22:16:55]

Patchset 2 (id:??) landed as
https://crrev.com/f07421508221dfcca43a6c10ad8e9047f8f8fcdf
Cr-Commit-Position: refs/heads/master@{#40648}