No mention of the proposed #private properties, hm.
Why should they mention them, though? They're still at stage 2, there's still time to reject them.
But if they'll get to 4, I think it will be time for TypeScript 3.
Hmm I'm not sure, TypeScript already has its private keyword. I would assume they are going to support both and compile it down to either a #private or not, depending on your target.
TypeScript is meant to be an extension of JavaScript. If it implements one of JavaScrpt's features in yet another way, I think it could be a stretch.
Then again, they *could* compile both syntaxes while deprecating the legacy one, I guess. But that would require a new major version (although TS does *not* follow semver).