[interpreter] Deprecate notion of an unreachable environment.

[interpreter] Deprecate notion of an unreachable environment.

The notion of an unreachable environment is useful for a recursive
descent iteration (e.g. over an AST) where nodes are created on the
ascent path as well. For a flat iteration (e.g. over bytecode stream)
environments become unreachable at the end of a visitation function.
Hence any unreachable path can be represented by nulling the tracked
environment completely. This further reduces the number of redundant
nodes being created.

R=oth@chromium.org

Committed: https://crrev.com/7d07a6c48901db92f3e6fd1cc84b55b8453d38f9
Cr-Commit-Position: refs/heads/master@{#33639}

[Michael Starzinger, 2016-01-29 14:52:07]

Description was changed from

==========
[interpreter] Deprecate notion of an unreachable environment.

The notion of an unreachable environment is usefull for a recursive
descent iteration (e.g. over an AST) where nodes are created on the
ascent path as well. For a flat iteration (e.h. over bytecode stream)
environments become unreachable at the end of a visitation function.
Hence any unreachable path can be represented by nulling the tracked
environment completely. This further reduces the number of redundant
nodes being created.

R=oth@chromium.org
==========

to

==========
[interpreter] Deprecate notion of an unreachable environment.

The notion of an unreachable environment is useful for a recursive
descent iteration (e.g. over an AST) where nodes are created on the
ascent path as well. For a flat iteration (e.h. over bytecode stream)
environments become unreachable at the end of a visitation function.
Hence any unreachable path can be represented by nulling the tracked
environment completely. This further reduces the number of redundant
nodes being created.

R=oth@chromium.org
==========

[Michael Starzinger, 2016-01-29 14:52:16]

mstarzinger@chromium.org changed reviewers:
+ bmeurer@chromium.org

[Michael Starzinger, 2016-01-29 14:53:28]

Description was changed from

==========
[interpreter] Deprecate notion of an unreachable environment.

The notion of an unreachable environment is useful for a recursive
descent iteration (e.g. over an AST) where nodes are created on the
ascent path as well. For a flat iteration (e.h. over bytecode stream)
environments become unreachable at the end of a visitation function.
Hence any unreachable path can be represented by nulling the tracked
environment completely. This further reduces the number of redundant
nodes being created.

R=oth@chromium.org
==========

to

==========
[interpreter] Deprecate notion of an unreachable environment.

The notion of an unreachable environment is useful for a recursive
descent iteration (e.g. over an AST) where nodes are created on the
ascent path as well. For a flat iteration (e.g. over bytecode stream)
environments become unreachable at the end of a visitation function.
Hence any unreachable path can be represented by nulling the tracked
environment completely. This further reduces the number of redundant
nodes being created.

R=oth@chromium.org
==========

[oth, 2016-02-01 09:09:41]

lgtm. Thank you for producing this run in manageable bitesized pieces.

[Michael Starzinger, 2016-02-01 11:54:10]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2016-02-01 11:54:22]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1650483003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1650483003/1

[commit-bot: I haz the power, 2016-02-01 12:17:56]

Description was changed from

==========
[interpreter] Deprecate notion of an unreachable environment.

The notion of an unreachable environment is useful for a recursive
descent iteration (e.g. over an AST) where nodes are created on the
ascent path as well. For a flat iteration (e.g. over bytecode stream)
environments become unreachable at the end of a visitation function.
Hence any unreachable path can be represented by nulling the tracked
environment completely. This further reduces the number of redundant
nodes being created.

R=oth@chromium.org
==========

to

==========
[interpreter] Deprecate notion of an unreachable environment.

The notion of an unreachable environment is useful for a recursive
descent iteration (e.g. over an AST) where nodes are created on the
ascent path as well. For a flat iteration (e.g. over bytecode stream)
environments become unreachable at the end of a visitation function.
Hence any unreachable path can be represented by nulling the tracked
environment completely. This further reduces the number of redundant
nodes being created.

R=oth@chromium.org
==========

[commit-bot: I haz the power, 2016-02-01 12:17:56]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-01 12:18:16]

Description was changed from

==========
[interpreter] Deprecate notion of an unreachable environment.

The notion of an unreachable environment is useful for a recursive
descent iteration (e.g. over an AST) where nodes are created on the
ascent path as well. For a flat iteration (e.g. over bytecode stream)
environments become unreachable at the end of a visitation function.
Hence any unreachable path can be represented by nulling the tracked
environment completely. This further reduces the number of redundant
nodes being created.

R=oth@chromium.org
==========

to

==========
[interpreter] Deprecate notion of an unreachable environment.

The notion of an unreachable environment is useful for a recursive
descent iteration (e.g. over an AST) where nodes are created on the
ascent path as well. For a flat iteration (e.g. over bytecode stream)
environments become unreachable at the end of a visitation function.
Hence any unreachable path can be represented by nulling the tracked
environment completely. This further reduces the number of redundant
nodes being created.

R=oth@chromium.org

Committed: https://crrev.com/7d07a6c48901db92f3e6fd1cc84b55b8453d38f9
Cr-Commit-Position: refs/heads/master@{#33639}
==========

[commit-bot: I haz the power, 2016-02-01 12:18:17]

Patchset 1 (id:??) landed as
https://crrev.com/7d07a6c48901db92f3e6fd1cc84b55b8453d38f9
Cr-Commit-Position: refs/heads/master@{#33639}