Open Bug 1341789 Opened 3 years ago Updated 3 years ago
IR: Don't eagerly emit IR with maybe Guard Int32Index
Currently maybeGuardInt32Index will always emit a index guard when called. This is too restrictive. For example currently we can't move tryAttachProxyElement after tryAttachTypedElement. This also prevents us from optimizing indexing with a string into primitive strings or magic arguments.
I tried this out before, but I don't like the way it turned out much. I am not sure arguments we should pass to the tryAttachXXX functions.
You need to log in before you can comment on or make changes to this bug.