mengzhx/deepseek-harness
1
0
Fork 0
mirror of https://github.com/deepseek-ai/deepseek-harness.git synced 2026-09-11 04:00:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(code-runtime): drop the remaining shipped claims for the private experimental backend

Browse Source 
The review's final wording items: the portable-identifier note's Scope said the
backend 'has since shipped' without noting it is experimental/private; the
RESERVED_WORDS JSDoc said backends 'ship for both languages'. Both now name the
TypeScript backend as released and the CPython backend as experimental and
private. The package README also records that the truncation-marker text and
tempdir prefix keep the pre-rename short names (byte-anchored by tests,
independent of the npm name).
This commit is contained in:
Chinesezjc
2026-08-31 15:19:22 +08:00
committed by Tianyi Cui
parent 12d0bdb274
commit c435170a93
4 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/code-runtime/code-runtime/src/index.ts
+2 -2
View File
@@ -66,8 +66,8 @@ export const DUNDER_MEMBER = /^__.+__$/
/**
* Reserved words of every portable target language (ECMAScript ∪ Python),
* refused as {@link CodeBindingNamespace.global} / error-class names by all
* backends, which ship for both languages: the TypeScript worker thread and
* the CPython subprocess. The portable-identifier contract
* backends, one per language: the released TypeScript worker thread and the
* experimental, private CPython subprocess. The portable-identifier contract
* promises a namespace list valid on one backend is valid on every backend; a
* per-language check would let `lambda` pass the TypeScript backend and fail
* the Python one. Extending the seam with a new language means widening this