<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section! Please help us by doing the following steps before logging an issue: * Search: https://github.com/Microsoft/TypeScript/search?type=Issues * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ Please fill in the *entire* template below. --> <!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. --> **TypeScript Version:** 2.9.0-dev.20180509 <!-- Search terms you tried before logging this (so others can find this issue more easily) --> **Search Terms:** **Code** ```ts function f<T>(x: T) { const y: object | null | undefined = x; } ``` in 2.8 with `strictNullChecks` on, this _compiles_ (it does not when it is off). In very recent `master`, however, it is now an error (as it should be?):  [**Playground Link**](http://www.typescriptlang.org/play/#src=function%20f%3CT%3E(x%3A%20T)%20%7B%0A%20%20%20%20const%20y%3A%20object%20%7C%20null%20%7C%20undefined%20%3D%20x%3B%0A%7D) While I think the error is certainly correct to issue, this change apparently breaks a handful of RWC tests, so is worth looking into.