Skip to content

[browser][coreCLR] Improve reporting for missing calli key #133124

Open

Description

@pavelsavara

Null thunk can be reached by Reflection or Reflection.Emit when the user app dynamically emits interop call for a signature that we have not discovered at build time.
We may want to have better error reporting story than printing "WASM calli missing for key" to stdout in that case

From @jkotas 's comment

Activity

  1. added this to the Future milestone on Sep 2, 2026
  2. dotnet-policy-service commented on Sep 2, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
    See info in area-owners.md if you want to be subscribed.

  3. dotnet-policy-service commented on Sep 2, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @JulieLeeMSFT, @BrzVlad, @janvorli
    See info in area-owners.md if you want to be subscribed.

  4. modified the milestones: Future, 12.0.0 on Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions