Closed loynoir closed 12 months ago
Error.stackTraceLimit is not part of the standard.
Duplicate of #188.
@ljharb
Sorry for duplicate.
Opened #118, and github prompted a failure.
Two problems.
Error.stackTraceLimit
now I know it's not part of the standard.
I think maybe it's safer to have something like SuppressedError.totalErrorNumbersLimit
, prevent somehow run within a loop within nested dependency.
There's no such concept in the spec, so it wouldn't make sense for this proposal to have it either.
File an issue on the only implementation that has that property - v8, i believe - and they'll decide if they need to address it.
@ljharb
There's no such concept in the spec, so it wouldn't make sense for this proposal to have it either.
As far as I know, there wasn't something like multiple errors.
But now there is SuppressedError
at stage 3.
A SuppressedError.totalErrorNumbersLimit
seems safer.
Still have a concern, just close as not an very usual case.
Thre is
Error.stackTraceLimit
What happen when situation
libraryA use
SuppressedError
libraryB use librayA
client call libraryB within a loop
Is there a
SuppressedError.sizeLimit
?