Implement Error.captureStackTrace

Open
#1,016 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
compilers

Research direction

Start with the existing lazy Error stack data, Error.prototype.stack accessors, CallStack, and stack formatting implementation. Read the current TC39 proposal, then inspect related language and built-in documentation, the Goccia proposal inventory, and existing tests. Done means the focused project tests, pinned Test262/proposal coverage, formatting, and documentation checks pass without regressions.

Written by the indexing model from the issue text.

Description

engine new feature spec compliance

Summary

Implement the Stage 2 TC39 proposal: https://github.com/tc39/proposal-error-capturestacktrace

Add captureStackTrace(target[, constructorOpt]) with arbitrary-object mutation, frame elision, descriptors, and proposal errors.

Why

This proposal fits GocciaScript's modern ECMAScript surface and the 0.13.0 proposal roadmap. It should extend the engine's existing architecture rather than arrive as a userland shim.

Current behavior

Lazy Error stack data and Error.prototype.stack accessors exist, but Error.captureStackTrace is absent.

Expected behavior

Add captureStackTrace(target[, constructorOpt]) with arbitrary-object mutation, frame elision, descriptors, and proposal errors.

Scope notes

Reuse CallStack and existing formatting; do not add prepareStackTrace or structured frames. Cover Error/non-Error targets, proxies, non-extensible objects, existing stack properties, missing cutoffs, realms, bound/native functions, docs, and tests. Additive API: no flag.

Related bytecode roadmap: #871 and #875. Update the relevant language/built-in documentation and Goccia proposal inventory. Use the proposal repository and its current specification at implementation time; add focused project tests and matching pinned Test262/proposal coverage without regressions.

Acceptance criteria

  • Parser/API surface, descriptors, evaluation order, errors, and observable protocol behavior match the current proposal.
  • Implementation uses the identified shared engine seam without a duplicate compatibility shim.
  • Focused positive, negative, abrupt-completion, and edge-case tests cover the proposal.
  • Relevant project suites, pinned Test262 cases, formatting, and documentation checks pass.
Dominant language
Pascal
Stars
20
Forks
3
Avg merge
3d 4h
Merged PRs (30d)
45

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 frostney/GocciaScript

All issues in frostney/GocciaScript

Similar issues

More Compilers issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.