Andrew Branch

I think this aliasing unsoundness is actually unrelated to whether `(...args: never) => void` is callable. Consider `(...args: never[]) => void` or even `(...args: string[]) => void`. The assignment to...

> Otherwise, without `(...args: never) => unknown`, there is no top-type for all functions. Well, `(...args: never[]) => unknown` is still a function top type in that every other function...

> Well, `(...args: never[]) => unknown` is still a function top type in that every other function type is assignable to it Actually I found a counterexample from AnyhowStep by...

You just need to [commit the baseline changes](https://github.com/microsoft/TypeScript/blob/main/CONTRIBUTING.md#managing-the-baselines), assuming they look ok. If you’re not sure if they look ok, commit them anyway so we can take a look.

Chances are most/all of them are just position changes of symbols defined after Object.freeze in lib.es5.d.ts since they will have moved up a few lines.

@typescript-bot test this @typescript-bot user test this inline @typescript-bot run dt

@DanielRosenwasser I’m fairly convinced this is right, but maybe we should plan to merge this for 4.9?

Thanks @nicolas377!

> With what default conditions (configurable?) and what behavior for the import/require conditions? `import` or `require` based on importing syntax (if we allow `require` to resolve at all); additional conditions...

@jakebailey I believe you’re thinking of ts-loader, but only in “full mode” as opposed to `transpileOnly`, which has been in the back of my mind to look into, but basically...