GitNexus/gitnexus/test/fixtures/lang-resolution/ts-chain-interface-dispatch/app.ts

import { Deps } from './deps';

// `r` is a bare-name receiver whose type binding is the member expression
// `d.repo` — the chain-typebinding shape that reaches Case 3b. The fold lands
// on the Repo INTERFACE, so the primary edge targets Repo.save and the
// implementations are reachable only through the interface-dispatch fan-out.
export function runSave(d: Deps): void {
    const r = d.repo;
    r.save('row');
}

// Same shape, concrete owner: Case 3b resolves PlainCache, which is not an
// Interface, so the fan-out must stay inert.
export function runCache(d: Deps): void {
    const c = d.cache;
    c.run();
}

// Stronger negative than runCache: SqlRepo IMPLEMENTS Repo, so an interface is
// in scope at this site and `save` is a name Repo also declares. The fan-out
// must still stay inert, because the fold produced the concrete class — the
// receiver's runtime type is SqlRepo, not "any Repo". This is what fails if a
// later change fans out from the interface a member is DECLARED in rather than
// from the receiver's own folded type.
export function runConcrete(d: Deps): void {
    const s = d.sql;
    s.save('row');
}