Message from JavaScript discussions

November 2018

— Can you stop after otherThing is called, but before thing is called in both cases?


All the middle step would do is push the value into the user code, only for it to come right back out again inside the instruction token of thing

— I see

— Alright, I'm for it now

— So the dispatcher could instead just make the instruction token right there

— These kinds of optimizations are good

— But consider:
thing(foo = otherThing())

— Give it import$ polyfill, wat is the output? im on mobile

— It's tiny, but if it happens a lot then it saves a lot of heap dumping

— All possible cases must be handled

— Yeah, this would require control to be handed back

— I have never seen those constructions, what they do?