* fix(prompt-hook): fire the structural gate for Latin-script, Cyrillic, and JA/KO prompts (#1126) The prompt-hook's keyword gate only knew English and simplified-Chinese keywords, so a structural question in French (or Spanish, German, Italian, Portuguese, Russian, Japanese, Korean, traditional Chinese) silently no-op'd unless it happened to contain an identifier-shaped code token — the #994 symptom, resurfaced for every other language. Root causes fixed: - JS \b is ASCII-only: a keyword whose first/last char is accented or non-Latin (où, qué, Cyrillic, kana) can never match \bkeyword\b — the same mechanism behind #994. Keyword matching now uses Unicode lookaround boundaries ((?<![\p{L}\p{N}_]) … (?![\p{L}\p{N}_])). - Bare-stem English entries never matched their own derived forms (\barchitect\b can't match "architecture", \bdepend\b can't match "dependencies"). Stems are now matched as word prefixes (leading boundary only), which also lets one shared stem cover the Romance/ Germanic spellings that coincide. - The "CJK" set was simplified-Chinese-only: Japanese (呼び出し, 仕組み, 実装 — and 追跡 ≠ 追踪), Korean, and traditional-Chinese terms are now in the unsegmented substring set. Code-token extraction and the graph-verification path are unchanged; non-structural prose stays a zero-cost no-op in every language. Fixes #1126 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(prompt-hook): extend the gate to tier-2 languages (VI/TR/ID/PL/UA/NL/CS/RO/HU/EL/Nordics/FI/HI/AR/FA/HE/TH) The first pass covered the 10 largest languages; this closes the rest of the major-developer-population set (~29 total). Notable per-language mechanics the curation had to respect: - Agglutinative languages (Turkish, Finnish, Hungarian) need stems, not exact words — suffixes attach to everything (akışı, riippuu, működik). - Indonesian me-/di-/ber- prefixes block leading-boundary stems, so affixed forms are listed explicitly (memanggil, dipanggil, berfungsi). - Arabic/Farsi/Hebrew are spaced but proclitics attach to the word (وكيف = and-how), so they join the substring class with Thai. - Ukrainian і/и spellings diverge from Russian (архітектур ≠ архитектур). - Excluded terms that collide with English or code words: NL "pad", SV "var", CS "tok", Catalan "com" (matches every .com domain) — with regression tests pinning the exclusions. Vietnamese was the sharpest gap: spaced Latin with heavy diacritics — exactly the ASCII-\b failure class #1126 reports. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Colby Mchenry
co-authored by
Claude Fable 5
Claude Fable 5
parent
04e23917d0
commit
317e7f4d3d
+194
-19
@@ -234,36 +234,211 @@ export function findIndexedSubprojectRoots(
|
||||
}
|
||||
|
||||
/**
|
||||
* English structural keywords, matched with `\b` word boundaries so a keyword
|
||||
* inside a longer word doesn't false-positive ("flow" in "flower").
|
||||
* Unicode-aware word-boundary emulation for the keyword lists below. JS's `\b`
|
||||
* is ASCII-only — it fires only at `[A-Za-z0-9_]` edges — so it can never bound
|
||||
* a keyword whose first or last character is accented or non-Latin: `/\boù\b/`
|
||||
* NEVER matches "où est …" (ù isn't an ASCII word char, so no boundary exists
|
||||
* next to it). That is the #994 CJK mechanism resurfaced for Latin scripts and
|
||||
* Cyrillic (#1126). A lookaround — "not flanked by a letter, digit, or
|
||||
* underscore" — is the script-independent equivalent.
|
||||
*/
|
||||
const STRUCTURAL_EN = /\b(how|where|trace|flow|path|reach(?:es|ed)?|call(?:s|ed|er|ers|ee)?|depend|impact|affect|wired?|connect|implement|architect|structure|breaks?|what calls|why does)\b/i;
|
||||
const NOT_WORD_BEFORE = /(?<![\p{L}\p{N}_])/u.source;
|
||||
const NOT_WORD_AFTER = /(?![\p{L}\p{N}_])/u.source;
|
||||
|
||||
/**
|
||||
* Non-English (CJK) structural keywords, matched WITHOUT `\b`. JS's `\b` is
|
||||
* ASCII-only — it only fires at `[A-Za-z0-9_]` boundaries, never between Han
|
||||
* characters — so a Chinese keyword wrapped in `\b…\b` could never match. That
|
||||
* was issue #994: the English-only gate silently no-op'd every Chinese prompt,
|
||||
* so non-English users got no front-load nudge and no error to explain why. The
|
||||
* set mirrors the English intent (如何=how, 在哪/哪里=where, 流程/流向=flow,
|
||||
* 路径=path, 调用=call, 依赖=depend, 影响=impact/affect, 实现=implement,
|
||||
* 架构=architect, 结构=structure, 追踪/跟踪=trace) plus structural-overview words
|
||||
* with no single clean English equivalent (介绍/解析/分析/原理/机制).
|
||||
* Structural keywords matched as EXACT words (boundary on both sides): short
|
||||
* or ambiguous tokens where prefix matching would false-positive ("flow" in
|
||||
* "flower", "path" in "pathological"). Grouped by language; a term appears once
|
||||
* even when several languages share it ("como" is Portuguese for how AND
|
||||
* unaccented-typed Spanish "cómo").
|
||||
*/
|
||||
const STRUCTURAL_CJK = /如何|怎么|在哪|哪里|追踪|跟踪|流程|流向|路径|调用|依赖|影响|实现|架构|结构|介绍|解析|分析|原理|机制/;
|
||||
const STRUCTURAL_WORDS = [
|
||||
// English — the pre-#1126 list minus what moved to STRUCTURAL_STEMS: the
|
||||
// bare-stem entries never matched their own derived forms (`\barchitect\b`
|
||||
// can't match "architecture"), and "what calls" is subsumed by the "call" stem.
|
||||
'how', 'where', 'tracing', 'flows?', 'paths?', 'reach(?:es|ed)?', 'wired?', 'breaks?', 'why does',
|
||||
// French (où=where, flux=flow, chemin=path, casse=breaks)
|
||||
'comment', 'où', 'flux', 'chemins?', 'casse',
|
||||
// Spanish (cómo/como=how, dónde/donde=where, flujo=flow, ruta/camino=path,
|
||||
// rompe=breaks, llaman / quién llama = call(s) — bare "llama" is excluded:
|
||||
// it's also the animal/model name in English prompts)
|
||||
'cómo', 'dónde', 'donde', 'flujos?', 'rutas?', 'caminos?', 'rompe', 'llaman', 'quién llama', 'quien llama',
|
||||
// Portuguese (como=how — also covers unaccented Spanish; onde=where,
|
||||
// fluxo=flow, caminho=path)
|
||||
'como', 'onde', 'fluxos?', 'caminhos?',
|
||||
// German (wie=how, wo/woher/wohin=where, Pfad=path, Fluss/Ablauf=flow,
|
||||
// bricht/kaputt=breaks, ruft=calls, hängt=depends — "hängt … von X ab"
|
||||
// splits the separable verb "abhängen", so the "abhäng" stem can't catch it)
|
||||
'wie', 'wo', 'woher', 'wohin', 'pfade?', 'fluss', 'ablauf', 'bricht', 'kaputt', 'ruft', 'hängt',
|
||||
// Italian (dove=where, flusso=flow, percorso/i=path)
|
||||
'dove', 'flusso', 'percors[oi]',
|
||||
// Russian (как=how, где=where, путь/пути=path, работает=works)
|
||||
'как', 'где', 'путь', 'пути', 'работает',
|
||||
// Ukrainian (як=how, де=where, потік=flow — обліque cases reuse the RU
|
||||
// "поток" stem; працює=works)
|
||||
'як', 'де', 'потік', 'працює',
|
||||
// Dutch (hoe=how, waar=where, roept=calls, werkt=works, aangeroepen=called —
|
||||
// the ge- participle escapes the "aanroep" stem)
|
||||
'hoe', 'waar', 'roept', 'werkt', 'aangeroepen',
|
||||
// Polish + Czech (jak=how — shared; gdzie/kde=where, cesta=path)
|
||||
'jak', 'gdzie', 'kde', 'cesta',
|
||||
// Romanian (cum=how, unde=where; flux is shared with French)
|
||||
'cum', 'unde',
|
||||
// Hungarian (hogyan=how, hol=where)
|
||||
'hogyan', 'hol',
|
||||
// Turkish (nasıl=how, mimari=architecture, takip=trace/follow)
|
||||
'nasıl', 'mimari', 'takip',
|
||||
// Indonesian/Malay (bagaimana=how, di mana/dimana=where, alur=flow, jalur=path)
|
||||
'bagaimana', 'di mana', 'dimana', 'alur', 'jalur',
|
||||
// Vietnamese — spaced Latin with heavy diacritics, the exact class ASCII `\b`
|
||||
// breaks (làm sao/thế nào=how, ở đâu=where, gọi=call, phụ thuộc=depend,
|
||||
// ảnh hưởng=affect, kiến trúc=architecture, cấu trúc=structure, luồng=flow,
|
||||
// đường dẫn=path, hoạt động=works, giải thích=explain, theo dõi=trace)
|
||||
'làm sao', 'thế nào', 'ở đâu', 'gọi', 'phụ thuộc', 'ảnh hưởng', 'kiến trúc',
|
||||
'cấu trúc', 'luồng', 'đường dẫn', 'hoạt động', 'giải thích', 'theo dõi',
|
||||
// Swedish / Danish / Norwegian (hur/hvordan=how, hvor=where, beror=depends,
|
||||
// flöde=flow)
|
||||
'hur', 'hvordan', 'hvor', 'beror', 'flöde',
|
||||
// Finnish (miten=how, missä=where, toimii=works)
|
||||
'miten', 'missä', 'toimii',
|
||||
// Greek (πώς=how, πού=where — accented forms only: unaccented πως/που are
|
||||
// ubiquitous conjunctions; καλεί=calls, δομή=structure, ροή=flow)
|
||||
'πώς', 'πού', 'καλεί', 'δομή', 'ροή',
|
||||
// Hindi (कैसे=how, कहाँ/कहां=where, कॉल=call, निर्भर=depends,
|
||||
// संरचना=structure, प्रवाह=flow)
|
||||
'कैसे', 'कहाँ', 'कहां', 'कॉल', 'निर्भर', 'संरचना', 'प्रवाह',
|
||||
];
|
||||
|
||||
/**
|
||||
* Structural keyword STEMS matched as word PREFIXES (boundary on the left
|
||||
* only), so derived forms match without enumerating each: "architect" fires on
|
||||
* architecture/architectural, "depend" on depends/dependency/dependencies,
|
||||
* "вызыва" on вызывает/вызывается. Mid-word occurrences stay excluded —
|
||||
* "restructure"/"independent" don't fire — so precision stays close to the
|
||||
* exact-word class. Add a stem only when every plausible completion is still a
|
||||
* structural word.
|
||||
*/
|
||||
const STRUCTURAL_STEMS = [
|
||||
// English + the Latin-script languages that share the spelling (French
|
||||
// architecture/structure/trace/impact, Spanish depende/implementa/impacto, …)
|
||||
'architect', 'structur', 'depend', 'implement', 'connect', 'impact', 'affect', 'trace', 'call', 'explain',
|
||||
// French (appel(le)=call, dépend=depends, implément(e)=implement,
|
||||
// connex(ion)=connection, expliqu(e)=explain, fonctionn(e/ement)=works)
|
||||
'appel', 'dépend', 'implément', 'connex', 'expliqu', 'fonctionn',
|
||||
// Spanish (llamad(a)=call, afect(a)=affect, conect(a)/conexi(ón)=connect,
|
||||
// arquitec(tura)=architecture, estructur(a)=structure, funcion(a)=works,
|
||||
// traza(r)=trace, explica=explain)
|
||||
'llamad', 'afect', 'conect', 'conexi', 'arquitec', 'estructur', 'funcion', 'traza', 'explica',
|
||||
// Portuguese (chama(da)=call, afeta=affect, arquitet(ura)=architecture,
|
||||
// estrutur(a)=structure, quebra(do)=breaks)
|
||||
'chama', 'afeta', 'arquitet', 'estrutur', 'quebra',
|
||||
// German (abhäng(t)=depend, Auswirkung=impact, beeinfluss(t)=affect,
|
||||
// verbind(et)=connect, Architektur, Struktur, funktionier(t)=works,
|
||||
// Aufruf/aufgerufen=call, erklär(t)=explain, verfolg(en)=trace)
|
||||
'abhäng', 'auswirkung', 'beeinfluss', 'verbind', 'architekt', 'struktur', 'funktionier', 'aufruf', 'aufgerufen', 'erklär', 'verfolg',
|
||||
// Italian (chiam(a/ata)=call, dipend(e/enza)=depend, impatt(o)=impact,
|
||||
// connett(e)/conness(ione)=connect, architett(ura), struttur(a),
|
||||
// funzion(a/amento)=works, tracci(a)=trace, spiega(mi)=explain)
|
||||
'chiam', 'dipend', 'impatt', 'connett', 'conness', 'architett', 'struttur', 'funzion', 'tracci', 'spiega',
|
||||
// Russian (вызыва(ет)=calls, завис(ит)=depends, влия(ет)=affects,
|
||||
// реализ(ация)=implementation, структур(а), архитектур(а),
|
||||
// трассир(овка)=trace, лома(ет)=breaks, объясн(и)=explain, поток=flow)
|
||||
'вызыва', 'завис', 'влия', 'реализ', 'структур', 'архитектур', 'трассир', 'лома', 'объясн', 'поток',
|
||||
// Ukrainian — і/и spellings diverge from Russian (виклика(є)=calls,
|
||||
// залеж(ить)=depends, вплива(є)=affects, архітектур(а), реаліз(ація),
|
||||
// поясн(и)=explain, шлях(у)=path; структур(а) is shared with Russian)
|
||||
'виклика', 'залеж', 'вплива', 'архітектур', 'реаліз', 'поясн', 'шлях',
|
||||
// Dutch (aanroep(en)=call, afhankelijk(heid)=depends, beïnvloed(t)=affects,
|
||||
// structuur — "structur" can't reach the uu; uitleg(gen)=explain)
|
||||
'aanroep', 'afhankelijk', 'beïnvloed', 'structuur', 'uitleg',
|
||||
// Polish (wywoł(uje)=calls, zależ(y)=depends, wpływ(a)=affects/impact,
|
||||
// przepływ=flow, ścieżk(a)=path, działa(nie)=works, wyjaśni(j)=explain,
|
||||
// śledz(enie)=trace; architektura/struktura fire via the German stems)
|
||||
'wywoł', 'zależ', 'wpływ', 'przepływ', 'ścieżk', 'działa', 'wyjaśni', 'śledz',
|
||||
// Czech (volá(ní)=calls, závis(í)=depends, ovlivň(uje)=affects,
|
||||
// funguj(e)=works, vysvětl(i)=explain)
|
||||
'volá', 'závis', 'ovlivň', 'funguj', 'vysvětl',
|
||||
// Romanian (apel(ează)=calls, depind(e)=depends — i not e, so "depend" misses
|
||||
// it; arhitectur(a) — no c; funcțion(ează)=works, explică=explain)
|
||||
'apel', 'depind', 'arhitectur', 'funcțion', 'explică',
|
||||
// Hungarian (hív(ja)=calls, függ(őség)=depends, működ(ik)=works,
|
||||
// struktúr(a) — ú escapes "struktur"; magyaráz(d)=explain;
|
||||
// architektúra fires via the German stem)
|
||||
'hív', 'függ', 'működ', 'struktúr', 'magyaráz',
|
||||
// Turkish — agglutinative, so stems beat exact words (nere(de/ye/den)=where,
|
||||
// çağır/çağrı=call, bağıml(ı)=depends, bağlant(ı)=connection, akış(ı)=flow,
|
||||
// etkile(r)/etkisi=affects/impact)
|
||||
'nere', 'çağır', 'çağrı', 'bağıml', 'bağlant', 'akış', 'etkile', 'etkisi',
|
||||
// Indonesian/Malay — me-/di-/ber- prefixes block a bare stem, so affixed
|
||||
// forms are listed too (panggil(an)/memanggil/dipanggil=call,
|
||||
// bergantung/tergantung=depends, pengaruh/mempengaruhi/memengaruhi=affect,
|
||||
// arsitektur=architecture, fungsi/berfungsi=works,
|
||||
// jelaskan/menjelaskan=explain)
|
||||
'panggil', 'memanggil', 'dipanggil', 'bergantung', 'tergantung', 'pengaruh',
|
||||
'mempengaruhi', 'memengaruhi', 'arsitektur', 'fungsi', 'berfungsi', 'jelaskan', 'menjelaskan',
|
||||
// Swedish / Danish / Norwegian (anrop(ar)=calls, påverk(ar)/påvirk(er)=affects,
|
||||
// afhæng(er)/avheng(er)=depends, förklar(a)/forklar=explain,
|
||||
// arkitektur — k not ch; funger(ar/er)=works)
|
||||
'anrop', 'påverk', 'påvirk', 'afhæng', 'avheng', 'förklar', 'forklar', 'arkitektur', 'funger',
|
||||
// Finnish (kutsu(u)=calls, riippu(u)=depends, arkkitehtuur(i),
|
||||
// rakente(en)=structure, selit(ä)=explain)
|
||||
'kutsu', 'riippu', 'arkkitehtuur', 'rakente', 'selit',
|
||||
// Greek — accented and unaccented stem spellings both occur
|
||||
// (εξαρτ(άται)=depends, επηρε(άζει)=affects, αρχιτεκτονικ(ή),
|
||||
// διαδρομ(ή)=path, εξηγ/εξήγ(ησε)=explain)
|
||||
'εξαρτ', 'επηρε', 'αρχιτεκτονικ', 'διαδρομ', 'εξηγ', 'εξήγ',
|
||||
// Hindi (समझा(ओ/इए)=explain, आर्किटेक्चर=architecture)
|
||||
'समझा', 'आर्किटेक्चर',
|
||||
];
|
||||
|
||||
const STRUCTURAL_WORDS_RE = new RegExp(`${NOT_WORD_BEFORE}(?:${STRUCTURAL_WORDS.join('|')})${NOT_WORD_AFTER}`, 'iu');
|
||||
const STRUCTURAL_STEMS_RE = new RegExp(`${NOT_WORD_BEFORE}(?:${STRUCTURAL_STEMS.join('|')})`, 'iu');
|
||||
|
||||
/**
|
||||
* Structural keywords matched as bare SUBSTRINGS, for languages where a
|
||||
* boundary can't be relied on: scripts with no word separators (Chinese —
|
||||
* simplified AND traditional; the original #994 set was simplified-only —
|
||||
* Japanese, Thai), Korean (spaced, but particles attach directly to the noun:
|
||||
* 구조가/구조를), and Arabic / Farsi / Hebrew (spaced, but proclitics attach to
|
||||
* the word: وكيف "and-how", והמבנה "and-the-structure"). JS's `\b` can never
|
||||
* fire between Han characters, which was issue #994: the English-only gate
|
||||
* silently no-op'd every Chinese prompt, so non-English users got no front-load
|
||||
* nudge and no error to explain why. The sets mirror the English intent
|
||||
* (如何/怎么/怎麼/どうやって/どのように/어떻게/كيف/چگونه/چطور/איך/อย่างไร/ยังไง=how,
|
||||
* 在哪/哪里/哪裡/어디/أين/كجا/איפה/ที่ไหน=where, 流程/流向/流れ/흐름/تدفق/זרימה=flow,
|
||||
* 路径/路徑/経路/경로/مسار/مسیر/נתיב/เส้นทาง=path,
|
||||
* 调用/調用/呼び出/호출/يستدعي/استدعاء/فراخوان/קורא/เรียกใช้=call,
|
||||
* 依赖/依賴/依存/의존/يعتمد/تعتمد/وابسته/תלוי/ขึ้นอยู่กับ=depend,
|
||||
* 影响/影響/영향/يؤثر/تأثير/تأثیر/משפיע/ผลกระทบ=impact/affect,
|
||||
* 实现/實現/実装/구현=implement,
|
||||
* 架构/架構/アーキテクチャ/아키텍처/معماري/معماری/ארכיטקטור/สถาปัตยกรรม=architecture,
|
||||
* 结构/結構/構造/구조/بنية/هيكل/ساختار/מבנה/โครงสร้าง=structure,
|
||||
* 追踪/跟踪/追蹤/追跡/トレース/추적/تتبع/ติดตาม=trace,
|
||||
* يعمل/تعمل/ทำงาน=works) plus structural-overview words with no single clean
|
||||
* English equivalent (介绍/介紹/解析/分析/原理/机制/機制/仕組み/説明/설명/動作/동작/작동/
|
||||
* اشرح/شرح/توضیح/הסבר/อธิบาย=explain).
|
||||
*/
|
||||
const STRUCTURAL_UNSEGMENTED = /如何|怎么|怎麼|在哪|哪里|哪裡|追踪|跟踪|追蹤|追跡|トレース|流程|流向|流れ|路径|路徑|経路|调用|調用|呼び出|依赖|依賴|依存|影响|影響|实现|實現|実装|架构|架構|アーキテクチャ|结构|結構|構造|介绍|介紹|解析|分析|原理|机制|機制|仕組み|説明|動作|どうやって|どのように|어떻게|어디|호출|흐름|경로|의존|영향|구현|구조|아키텍처|추적|동작|작동|설명|كيف|أين|اين|يستدعي|استدعاء|يعتمد|تعتمد|يؤثر|تأثير|معماري|بنية|هيكل|تدفق|مسار|تتبع|يعمل|تعمل|اشرح|شرح|چگونه|چطور|کجا|فراخوان|وابسته|تأثیر|معماری|ساختار|مسیر|توضیح|איך|איפה|קורא|תלוי|משפיע|ארכיטקטור|מבנה|זרימה|נתיב|הסבר|อย่างไร|ยังไง|ที่ไหน|เรียกใช้|ขึ้นอยู่กับ|ผลกระทบ|สถาปัตยกรรม|โครงสร้าง|เส้นทาง|ติดตาม|ทำงาน|อธิบาย/;
|
||||
|
||||
/** Doc/data/asset file extensions — a `name.ext` of this kind is a file
|
||||
* reference, not a code symbol, so it must not trip the member-access signal. */
|
||||
const DOC_DATA_EXT = /\.(md|markdown|txt|rst|json|ya?ml|toml|lock|csv|tsv|log|ini|cfg|conf|env|xml|html?|png|jpe?g|gif|svg|pdf)$/i;
|
||||
|
||||
/**
|
||||
* Does `prompt` contain an explicit structural keyword (English or CJK)? A
|
||||
* keyword is a strong, self-contained signal, so the front-load hook fires on it
|
||||
* directly — no graph check needed. (A *code-token* match, by contrast, is only
|
||||
* a candidate the hook verifies against the graph first; see {@link extractCodeTokens}.)
|
||||
* Does `prompt` contain an explicit structural keyword? A keyword is a strong,
|
||||
* self-contained signal, so the front-load hook fires on it directly — no graph
|
||||
* check needed. (A *code-token* match, by contrast, is only a candidate the
|
||||
* hook verifies against the graph first; see {@link extractCodeTokens}.)
|
||||
* Coverage is multilingual (#994, #1126): the ~29 languages with the largest
|
||||
* developer populations, across Latin, Cyrillic, Greek, CJK, Hangul, Arabic,
|
||||
* Hebrew, Thai, and Devanagari scripts. Languages beyond the keyword table
|
||||
* still fire through the language-agnostic code-token path.
|
||||
*/
|
||||
export function hasStructuralKeyword(prompt: string): boolean {
|
||||
return !!prompt && (STRUCTURAL_EN.test(prompt) || STRUCTURAL_CJK.test(prompt));
|
||||
return (
|
||||
!!prompt &&
|
||||
(STRUCTURAL_WORDS_RE.test(prompt) || STRUCTURAL_STEMS_RE.test(prompt) || STRUCTURAL_UNSEGMENTED.test(prompt))
|
||||
);
|
||||
}
|
||||
|
||||
/**
|
||||
@@ -303,7 +478,7 @@ export function extractCodeTokens(prompt: string): string[] {
|
||||
/**
|
||||
* Cheap, graph-free candidate gate for the front-load hook: could `prompt` be a
|
||||
* structural / flow / impact / "where-how" question worth front-loading context
|
||||
* for? True on an explicit keyword (English or CJK, issue #994) OR an
|
||||
* for? True on an explicit keyword in any covered language (#994, #1126) OR an
|
||||
* identifier-shaped token. A keyword is sufficient to fire on its own; a
|
||||
* token-only match is only a candidate the hook then verifies against the graph
|
||||
* (a brand name like `JavaScript` is token-shaped but isn't a symbol). Every
|
||||
|
||||
Reference in New Issue
Block a user