Make how stack trace propagates more abstract

This was suggested by @rossberg in WebAssembly#197 (comment).
aheejin · Feb 15, 2022 · 673af6a · 673af6a
1 parent 3dc715a
commit 673af6a
Showing 1 changed file with 3 additions and 3 deletions.
diff --git 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: