You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
Above, this will fail currently and not bail out because we don't support return in loop bodies. We can add support for this but it won't gain us too much by itself. What we really want to do be able to do is bail-out, then optimize the nested function generated. Somehow, we need to extract the "for" part so we can do this though (otherwise it will recursively keep generating a bailout loop).
@hermanventer@sebmarkbage any thoughts on how we might handle this pattern? Might it be that we actually should preference the original ES2015 code in this case until we can support these difficult problems in Prepack?
The text was updated successfully, but these errors were encountered:
Take the case:
Above, this will fail currently and not bail out because we don't support
return
in loop bodies. We can add support for this but it won't gain us too much by itself. What we really want to do be able to do is bail-out, then optimize the nested function generated. Somehow, we need to extract the "for" part so we can do this though (otherwise it will recursively keep generating a bailout loop).@hermanventer @sebmarkbage any thoughts on how we might handle this pattern? Might it be that we actually should preference the original ES2015 code in this case until we can support these difficult problems in Prepack?
The text was updated successfully, but these errors were encountered: