Skip to content

Commit 5d4bb9b

Browse files
authored
Update README.md
1 parent 91c33c3 commit 5d4bb9b

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

README.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,13 @@ To quote the [V8 documentation](https://v8.dev/docs/stack-trace-api):
3838
Unfortunately, the JSC implementation diverges from the V8 one:
3939

4040
- JSC attaches a string valued prop to the object provided, where V8 instead installs their stack-getter function.
41+
- It uses the JSC stack string format.
4142

42-
I would actually like to specify this like the JSC one. It's simpler.
43+
I would actually like to specify this like the JSC one. It's simpler. Similarly, the text for the contents of the stack string should probably be something along the lines of
4344

45+
> The contents of the stack string is a textual representation of the [execution context stack](https://tc39.es/ecma262/#execution-context-stack), however the actual format and contents are implemetation defined and should not be relied upon to be identical across implementations.
46+
47+
48+
## Related Work
49+
50+
- The [Error Stacks](https://github.com/mgaudet/proposal-error-capturestacktrace) proposal is almost a pre-requisite for this, as mostly the current spec doesn't really talk about stacks. However, for this proposal I'd argue

0 commit comments

Comments
 (0)