<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. --> **TypeScript Version:** 3.6.0-dev.20190603 <!-- Search terms you tried before logging this (so others can find this issue more easily) --> **Search Terms:** never, extends, generic, conditional type **Code** ``` type MakesSense = never extends never ? 'yes' : 'no' // Resolves to 'yes' type ExtendsNever<T> = T extends never ? 'yes' : 'no' type MakesSenseToo = ExtendsNever<{}> // Resolves to 'no' type Huh = ExtendsNever<never> // Expect to resolve to 'yes', actually resolves to never ``` **Expected behavior:** Huh should resolve to 'yes', as MakesSense does. **Actual behavior:** Huh resolves to never. For another variant, you can change ExtendsNever to ``` type ExtendsNever<T extends never> = T extends never ? 'yes' : 'no' ``` and ExtendsNever<never> still resolves to never. **Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior --> [Here](https://www.typescriptlang.org/play/index.html#src=type%20MakesSense%20%3D%20never%20extends%20never%20%3F%20'yes'%20%3A%20'no'%20%2F%2F%20Resolves%20to%20'yes'%0D%0A%0D%0Atype%20ExtendsNever%3CT%3E%20%3D%20T%20extends%20never%20%3F%20'yes'%20%3A%20'no'%0D%0A%0D%0Atype%20MakesSenseToo%20%3D%20ExtendsNever%3C%7B%7D%3E%20%2F%2F%20Resolves%20to%20'no'%0D%0Atype%20Huh%20%3D%20ExtendsNever%3Cnever%3E%20%2F%2F%20Should%20resolve%20to%20'yes'%2C%20actually%20resolves%20to%20never%20) **Related Issues:** <!-- Did you find other bugs that looked similar? --> None