From ed5c1db578f97fce8bdb73267f83a4fb90b316b5 Mon Sep 17 00:00:00 2001
From: ExE Boss <3889017+ExE-Boss@users.noreply.github.com>
Date: Wed, 3 Apr 2019 14:15:00 +0200
Subject: [PATCH] =?UTF-8?q?docs(faq):=20Mention=C2=A0TypeScript=C2=A03?=
 =?UTF-8?q?=E2=80=99s=20`unknown`=C2=A0type?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/org.eclipse.n4js.doc/src/faq/comparison-typescript.adoc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/org.eclipse.n4js.doc/src/faq/comparison-typescript.adoc b/docs/org.eclipse.n4js.doc/src/faq/comparison-typescript.adoc
index 53888fe781..5ec4ddd423 100644
--- a/docs/org.eclipse.n4js.doc/src/faq/comparison-typescript.adoc
+++ b/docs/org.eclipse.n4js.doc/src/faq/comparison-typescript.adoc
@@ -106,6 +106,8 @@ h| `any+` h| yes h| no |
 h| TypeScript h| `any` h| yes h| yes |  • footnote:[In TypeScript, implicit usage of `any` can be disallowed by means of a compiler flag.]
 |===
 
+TypeScript 3 introduced the `unknown` type which behaves like N4JS's `any` type, with the exception that it isn't currently being used by default and has to be declared explicitly.
+
 === Type Errors Are Show-Stoppers in N4JS
 
 N4JS has two general levels of issues reported by the compiler: *warning*  and *error*.