You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, it's set to error-handling-correctness-only, but the docs recommend setting it always or in-try-catch. Personally, I prefer the always style (it's consistent, has better stacktraces, and equal perf1)
Footnotes
Originally, it had worse perf (4 ticks vs 2), but they changed the spec so it's faster (1 tick vs 2), but then changed plain return to also use 1 tick, so perf is moot unless you're targeting older targets. ↩
The text was updated successfully, but these errors were encountered:
By default, it's set to
error-handling-correctness-only
, but the docs recommend setting italways
orin-try-catch
. Personally, I prefer thealways
style (it's consistent, has better stacktraces, and equal perf1)Footnotes
Originally, it had worse perf (4 ticks vs 2), but they changed the spec so it's faster (1 tick vs 2), but then changed plain return to also use 1 tick, so perf is moot unless you're targeting older targets. ↩
The text was updated successfully, but these errors were encountered: