[browser][coreCLR] Improve reporting for missing calli key
Open
arch-wasm
area-CodeGen-Interpreter-coreclr
os-browser
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Description
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](https://github.com/dotnet/runtime/pull/132965/changes#r3918347353)
Contributor guide
Research direction
Start with the linked comment and trace the existing WASM calli missing-key path that prints "WASM calli missing for key" to stdout. Determine the intended reporting behavior for dynamically emitted interop signatures, then verify that the missing-key case produces the agreed diagnostic instead of the current output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, wasm
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100