Two bytecodes correspond to that node, the first one has the tested value in the context top, and the next one has the test result (true or false).
The problem is that currently, only the second one is considered a message send (because of "it will jump"), but the receiver of the message at that moment is wrong (cause it should be the tested value and not true or false).
TODO: Consider the message send to be the first bytecode for inlined ifNil (and similar) so the message receiver can be retrieved.
The next bytecode could be considered the return value of the ifNil message send (which never happens in application level, because of optimizations)
maxwills
commented
1 year ago
Two bytecodes correspond to that node, the first one has the tested value in the context top, and the next one has the test result (true or false). The problem is that currently, only the second one is considered a message send (because of "it will jump"), but the receiver of the message at that moment is wrong (cause it should be the tested value and not true or false). TODO: Consider the message send to be the first bytecode for inlined ifNil (and similar) so the message receiver can be retrieved. The next bytecode could be considered the return value of the ifNil message send (which never happens in application level, because of optimizations)