Type printing does not detect that a name is shadowed in the current scope

🔎 Search Terms

global shadowed declarations

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed

⏯ Playground Link

Playground Link

💻 Code

// @strict: true
// @declaration: true
// @target: es2020

// @filename: a.ts
export const o = {[Symbol.iterator]: 1}

// @filename: b.ts

import { o } from "./a";
export class Symbol { }
export const g = o;

🙁 Actual behavior

The typeof of g is { [Symbol.iterator]: number; }. This leads to an incorrect declaration since Symbol is shadowed in the current scope

🙂 Expected behavior

The typeof of g is { [globalThis.Symbol.iterator]: number; }.

Additional information about the issue

No response

Reproduce el caso de generación de declaraciones del Playground Link usando a.ts y b.ts, con el Symbol exportado ocultando el nombre global. Empieza rastreando la impresión de tipos que produce la declaración para g. Se considera terminado cuando el tipo generado usa globalThis.Symbol.iterator en lugar del Symbol.iterator ocultado.