Right now we handle bottom values semantically needed for a SetLocal by vending a JSValue that roughly matches the predicted value for the non-bottom path. This comes up for op_iterator_open/next. Unfortunately, this still causes AI to be unhappy. If we had a constant cell that was understood by the DFG to be a bottom value (and presumably crashes whenever accessed), the DFG would generate better code for op_iterator_open/next.