Behavior when object is an error instances

Open
#2 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
compilers

Research direction

Start by reading the Error.captureStackTrace proposal and the linked proposal-error-stacks discussion. Resolve the behavior for objects with an [[ErrorData]] slot, including whether to reset internal error stack information without adding a private field or own stack property; done means the specification decision is agreed and recorded.

Written by the indexing model from the issue text.

Description

What should the behavior of Error.captureStackTrace be when the object provided is an object with an [[ErrorData]] slot?

My preference right now would be to reset the internal error stack info, but not add a new private field or own stack property (this is partially assuming that we standardize a prototype stack property for Errors in https://github.com/tc39/proposal-error-stacks)

Dominant language
No language data
Stars
15
Forks
5
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tc39/proposal-error-capturestacktrace

All issues in tc39/proposal-error-capturestacktrace

Similar issues

More Compilers issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.