Repository navigation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: experimental codemode #34677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: experimental codemode #34677
Changes from 1 commit
49f20b6b0aa6bfcad83abcaa5f283a6621c14527d271ffc731448f24acc1742ba12049a3bfba8cbcc67b79275e6394c37055aa8ccdc75ea0bc427b12726a7405b93465085a13c16bba82d9015c064c34bcc437b9e06a09951ea0ac90b4af62a13900cafcec4560fc7f27fbf7c231144f9a6fdc49be249a8f330de9431ba33b3c6d6fedae571b7f5658ca700fdca428c16f3c8eFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Interpreter-surface parity pass: - Real error values: the seven standard error constructors are callable globals; instanceof works for Error types (a specific type matches itself and Error, never a sibling) plus Date/RegExp/Map/Set/Array/ Object/Promise. Caught failures carry the name the equivalent real-JS failure would have — JSON.parse and invalid regex patterns are SyntaxError, unknown identifiers and TDZ access ReferenceError, assignment to a constant TypeError, a bad normalize form RangeError; anything without a specific analogue stays plain Error and internal class names never leak. JSON.parse failures now include the engine's position detail. Error values remain plain { name, message } data; the brand rides on a non-enumerable symbol, so serialization is unchanged and spread loses it like JS loses the prototype. - Array splice/fill/copyWithin and keys/values/entries; string localeCompare/normalize/trimLeft/trimRight; regex failures now name the offending pattern or flags, the engine reason, and how to fix it. - Sandbox values survive intra-sandbox checkpoints: Object.* helpers, coercions, and spread pass Date/RegExp/Map/Set through by reference (copyIn gained a preserving mode), so Object.values({d}).getTime() works. The host boundary — results, tool arguments, JSON.stringify — still serializes JSON forms exactly as documented. - Console formatting is total and deep: NaN/Infinity print literally, nested sandbox values render their friendly forms, opaque references become in-place markers, cycles render [Circular]; console can no longer fail a program. - maxOutputBytes lost its 32,000 default, completing uniform no-default limits: absent now means no truncation, for hosts that bound tool output themselves. Explicit values validate and truncate as before.Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Uh oh!
There was an error while loading. Please reload this page.