From 673af6aa09b70dc5b7d3af3e794cc46103e9ec81 Mon Sep 17 00:00:00 2001 From: Heejin Ahn Date: Tue, 15 Feb 2022 15:56:50 -0800 Subject: [PATCH] Make how stack trace propagates more abstract This was suggested by @rossberg in https://github.com/WebAssembly/exception-handling/pull/197#discussion_r806689938. --- proposals/exception-handling/Exceptions.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/proposals/exception-handling/Exceptions.md b/proposals/exception-handling/Exceptions.md index 42701ed2..66219013 100644 --- a/proposals/exception-handling/Exceptions.md +++ b/proposals/exception-handling/Exceptions.md @@ -459,9 +459,9 @@ conventions](https://webassembly.github.io/spec/web-api/index.html#conventions). When `ExceptionOption` is not provided or it does not contain `traceStack` entry, `traceStack` is considered `false` by default. -To preserve stack trace info when crossing the JS to Wasm boundary, `Exception` -can internally contain an optional `externref` value containing a stack trace -string, which is propagated when caught by `catch` and rethrown by `rethrow`. +To preserve stack trace info when crossing the JS to Wasm boundary, exceptions +can internally contain a stack trace, which is propagated when caught by `catch` +and rethrown by `rethrow`. More formally, the added interfaces look like the following: