TypeScript can change if it has to, and it's done so before (ES modules are
a good example of this). They try their best to be a strict superset of
ECMAScript, and this even goes as far as making type errors early warnings,
not early errors, by default (the latter would technically be a violation
of section 16, paragraph 3).
On Thu, Oct 13, 2016, 08:37 Kagami Rosylight <sascha...@outlook.com> wrote:
> Or `!.`, which unfortunately is now being used by TypeScript?
> es-discuss mailing list
es-discuss mailing list