Context
PR #1509 added extraction of computed class method names (e.g., ['property7'], ['generator10']). These methods are now stored with brackets as part of the name (e.g., the node name includes the full computed expression text).
Problem
There is no test asserting that the resolver can actually find these methods when called at a call site. If caller code references a method via obj[key]() or obj.property7(), the current name representation may cause resolution failures.
This was a pre-existing design choice in the native engine (not introduced in #1509), but the new WASM extraction makes it more visible and more likely to surface.
Action
- Add a resolution test for computed property name call sites.
- Verify that the parity benchmark correctly covers computed-property method calls, not just extraction.
- If the name representation causes silent resolution failures, align the representation across both engines.
Context
PR #1509 added extraction of computed class method names (e.g.,
['property7'],['generator10']). These methods are now stored with brackets as part of the name (e.g., the node name includes the full computed expression text).Problem
There is no test asserting that the resolver can actually find these methods when called at a call site. If caller code references a method via
obj[key]()orobj.property7(), the current name representation may cause resolution failures.This was a pre-existing design choice in the native engine (not introduced in #1509), but the new WASM extraction makes it more visible and more likely to surface.
Action