[ASDAlexander77]

Merge order: merge this only after ASDAlexander77/TypeScriptCompiler#554 is merged and in a deployed tslang release. tslang releases before it reject a @cppvtable class whose methods have bodies, so nvrhi_direct wouldn't compile.

Summary

NVRHI reports messages through nvrhi::IMessageCallback, an interface the application implements. This PR implements it in tslang: a @cppvtable class extending nvrhi.IMessageCallback whose message() has a body. tslang builds the C++ vtable for it (#554), and NVRHI calls it like a C++ object.

@cppvtable
class MessageLog extends nvrhi.IMessageCallback {
    message(severity: u8, text: string): void { ... }
}

let messageLog = new MessageLog();                  // a global: NVRHI holds a pointer the GC can't see
Donut_SetNvrhiMessageCallback(<Opaque>messageLog);  // before the app is created

Changes

• Bindings: nvrhi.IMessageCallback in both ABI files:

  • win32: _destructor, message;
  • linux: _completeDestructor, _deletingDestructor, message.

  IDevice::getMessageCallback is bound (slot 71 win32 / 72 linux), and MESSAGE_SEVERITY_* values are added. tools/check_nvrhi_slots.py checks IMessageCallback too: both ABIs match.

• Donut patch Donut-message-callback-all-apis: DeviceCreationParameters::messageCallback is now used on Vulkan and D3D11, as D3D12 already does. It applies cleanly after the other patches, both on a clean Donut checkout and on the already-patched submodule.

• Interop:

  • Donut_SetNvrhiMessageCallback(callback): the devices created afterwards get this callback (null restores Donut's).
  • Donut_LogNvrhiMessage(severity, text): Donut's own handling (logs; Fatal ends the program), for a callback that passes messages on.
  • check_interop_types.py: the callback pointer is listed as raw memory, like Donut_GetNvrhiDevice's.

• nvrhi_direct: MessageLog:

  • checks that device.getMessageCallback() is the object implemented here;
  • with -debug, closes a command list that was never opened. The validation layer reports that as an error and does nothing else, and the test checks NVRHI delivered it to MessageLog;
  • every other message goes on to Donut's log, so CTest still fails on real validation errors.

• Docs: core/nvrhi.ts header and README.

Testing

All runs used a local tslang built from main plus #554:

Platform	Result
Windows, CTest with -debug	headless.dx12/.vk, headless.donut.dx12/.vk and nvrhi_direct.dx12/.vk pass. A mutated copy that expects a different message text fails, as it should: the provoked error reached Donut's log, and the check reported NVRHI didn't call MessageLog
Windows, JIT	nvrhi_direct passes
Android x86_64 emulator (host GPU)	nvrhi_direct and headless pass. That covers getMessageCallback() only: the emulator has no validation layer, so message() isn't provoked there. The C++-to-tslang call under the Itanium ABI is covered by #554's g++ test
Android arm64	builds; not run

🤖 Generated with Claude Code