Skip to content

fix(parity): jelly-micro edge diffs after node fix (super-dispatch false positives + receiver-callee) #1506

@carlos-alm

Description

@carlos-alm

After #1471 closes the node gap (25 nodes → 0), 20 edge diffs remain in parity-compare.mjs --langs jelly-micro:

Type 1 — WASM produces extra false-positive super-dispatch edges (wasm>0, native=0):

  • super/super.js:B.mB.m (self-loop, conf=0.8)
  • super2/super2.js:B.mB.m (self-loop)
  • super4/super4.js:PostMixin.msuper/super.js:B.m (cross-fixture false positive)
  • super4/super4.js:PostMixin.s, PostMixin.<static> similar cross-fixture edges
  • this/this.js:f.hf.g (incorrect this-dispatch)

Type 2 — Native produces edges WASM misses (wasm=0, native>0):

  • classes2:G.constructorprototypes3:a / spread:a (conf=0.5, dyn=1)
  • fun:foosuper5:b / spread:b (conf=0.5, dyn=1)
  • receiver-callee-mixupo1.f/o2.fg missing in WASM (2 each)

Type 3 — WASM produces duplicate edges native doesn't (wasm=4, native=0):

  • receiver-callee-mixup:fg appears 4x in WASM vs 0x native

Root cause investigation needed per engine. These are pre-existing gaps not introduced by the node fix.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions