pharo-vm
pharo-vm copied to clipboard
Bug in InterpreterPrimitives >> primitiveNotIdentical
The primitive is mixing receiver and argument when should following otherObject
.
https://github.com/pharo-project/pharo-vm/blob/de760673b5f108d32576b47f4bbdfd3b230520b0/smalltalksrc/VMMaker/InterpreterPrimitives.class.st#L2889-L2902
I don't know if the case never arrived because of:
- special selectors - always enter through the "inlined" bytecode -> In that case, is the primitive necessary?
- Never forwarded - Is the argument resolved before the call? -> In that case, is the check necessary in the definition?
- JIT compiler - the primitive is always jitted, so this function is invoked almost never.
good catch :)