Skip to content

fix: accept readonly tuples as Set seeds - #384

Merged
ctate merged 1 commit into
mainfrom
fix/issue-373-readonly-set-constructor
Sep 23, 2026
Merged

ctate merged 1 commit into
mainfrom
fix/issue-373-readonly-set-constructor

Conversation

@ctate

@ctate ctate commented Sep 23, 2026

Copy link
Copy Markdown
Collaborator
  • Accept supported readonly tuples in static Set constructors while preserving single evaluation and insertion order.
  • Add differential coverage and refresh constructor diagnostics.

Fixes #373

- Accept supported readonly tuples in static Set constructors while preserving single evaluation and insertion order.
- Add differential coverage and refresh constructor diagnostics.

Fixes #373

Co-authored-by: Hagege Ruben <20857346+HagegeR@users.noreply.github.com>
@vercel

vercel Bot commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
scriptc Ready Ready Preview, v0 Sep 23, 2026 2:45am UTC

@ctate
ctate merged commit cc44afb into main Sep 23, 2026
20 checks passed

This branch was successfully deployed

1 active deployment
Preview 441c694b Deployed Sep 23, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

static: new Set(values) rejects a readonly tuple / as const array even when the element type is string

1 participant