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 the declaration-generation case from the Playground Link using a.ts and b.ts, with the exported Symbol shadowing the global name. Start by tracing the type printing that produces the declaration for g. Done means the generated type uses globalThis.Symbol.iterator rather than the shadowed Symbol.iterator.