Updates:
Labels: Area-Compiler Priority-Low
Comment #6 on issue 3179 by habl...@chromium.org: Closures are not inlined.
They should be.
https://code.google.com/p/v8/issues/detail?id=3179
(No comment was entered for this change.)
--
You received this message because this project is co
Comment #4 on issue 3179 by habl...@chromium.org: Closures are not inlined.
They should be.
https://code.google.com/p/v8/issues/detail?id=3179
Update done during clean-up of issue tracker.
--
You received this message because this project is configured to send all
issue notifications to th
Updates:
Status: Accepted
Labels: Type-FeatureRequest
Comment #3 on issue 3179 by habl...@chromium.org: Closures are not inlined.
They should be.
https://code.google.com/p/v8/issues/detail?id=3179
(No comment was entered for this change.)
--
You received this message because
Comment #2 on issue 3179 by yang...@chromium.org: Closures are not inlined.
They should be.
http://code.google.com/p/v8/issues/detail?id=3179
Ah yes. The closure is not tenured. That's why it's not being inlined.
Maybe we can use a better heuristic. Then again, this is exposed also
becaus
Updates:
Summary: Closures are not inlined. They should be.
Comment #1 on issue 3179 by yang...@chromium.org: Closures are not inlined.
They should be.
http://code.google.com/p/v8/issues/detail?id=3179
In the second example, function b is declared as function literal, and is
inlined
