Summary
In the jelly-micro parity fixture, this/this.js shows:
- WASM:
f.h(method) → f.g(method) conf=0.9 cha — correctly emitted
- Native: missing —
runPostNativeThisDispatch doesn't pick up this.g() inside f.h
f.h is a function-as-property assignment (f.h = function() { this.g(); }), not a regular class method. resolveThisDispatch('g', 'f.h', 'this', ...) correctly finds f.g by treating f as the class prefix. Native's runPostNativeThisDispatch re-parses files with WASM but may not be capturing this.g() calls when the enclosing function is a func-prop assignment (not in a class body).
Fix direction
Ensure runPostNativeThisDispatch correctly attributes this.g() calls inside func-prop methods (f.h = function() {}) to the func-prop caller node. The Rust engine may need to emit these as call sites with receiver='this' in the context of a func-prop definition.
Stacking
Found in #1472. Defer to a follow-up PR.
Summary
In the jelly-micro parity fixture,
this/this.jsshows:f.h(method) → f.g(method) conf=0.9 cha— correctly emittedrunPostNativeThisDispatchdoesn't pick upthis.g()insidef.hf.his a function-as-property assignment (f.h = function() { this.g(); }), not a regular class method.resolveThisDispatch('g', 'f.h', 'this', ...)correctly findsf.gby treatingfas the class prefix. Native'srunPostNativeThisDispatchre-parses files with WASM but may not be capturingthis.g()calls when the enclosing function is a func-prop assignment (not in a class body).Fix direction
Ensure
runPostNativeThisDispatchcorrectly attributesthis.g()calls inside func-prop methods (f.h = function() {}) to the func-prop caller node. The Rust engine may need to emit these as call sites withreceiver='this'in the context of a func-prop definition.Stacking
Found in #1472. Defer to a follow-up PR.