{"id":1679,"date":"2016-11-08T17:33:28","date_gmt":"2016-11-08T17:33:28","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/typescript\/?p=845"},"modified":"2019-02-20T10:45:59","modified_gmt":"2019-02-20T17:45:59","slug":"typescript-2-1-rc-better-inference-async-functions-and-more-2","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/typescript\/typescript-2-1-rc-better-inference-async-functions-and-more-2\/","title":{"rendered":"TypeScript 2.1 RC: Better Inference, Async Functions, and More"},"content":{"rendered":"

Today we’re happy to announce our release candidate for TypeScript 2.1! If you aren’t familiar with it, TypeScript<\/a> is a language that adds optional static types to JavaScript, and brings new features from ES6 and later to whatever JavaScript runtime you’re using.<\/p>\n

As usual you can get the RC through NuGet, or just by running<\/p>\n

\n
npm install -g typescript@rc<\/pre>\n<\/div>\n
You can then easily use the RC release with Visual Studio Code<\/a> or our Sublime Text Plugin<\/a>.<\/p>\n
You can also grab the TypeScript 2.1 installer for Visual Studio 2015<\/a> after getting Update 3<\/a>.<\/p>\n
While TypeScript 2.1 has a lot of great features coming up, we’d like to highlight how much more powerful TypeScript 2.1’s inference will be, as well as how much easier it will be to write asynchronous code in all runtimes.<\/p>\n
<\/a>Smarter Inference<\/h2>\n
TypeScript 2.1 now makes it easier to model scenarios where you might incrementally<\/em> initialize variables. Since a lot of code is written like this in JavaScript, this makes it even easier to migrate existing codebases to TypeScript.<\/p>\n
To understand better, let’s start off by talking about the any<\/code> type.<\/p>\n
Most of the time, if TypeScript can’t figure out the type of a variable, it will choose the any<\/code> type to be as flexible as possible without troubling you. We often call this an implicit<\/em> any<\/code> (as opposed to an explicit<\/em> one, where you would have written out the type).<\/p>\n
\n
let<\/span> x;      \/\/ implicitly 'any'<\/span>\nlet<\/span> y =<\/span> []; \/\/ implicitly 'any[]'<\/span>\n\nlet<\/span> z:<\/span> any<\/span>; \/\/ explicitly 'any'.<\/span><\/pre>\n<\/div>\n
From that point on, you can do anything you want with those values. For many people, that behavior was too loose, which is why the --noImplicitAny<\/code> option will warn you whenever a type couldn’t be inferred.<\/p>\n
With TypeScript 2.0 we built out a foundation of using control flow analysis to track the flow of types throughout your program. Because that analysis examines the assignments of every variable, we’ve leveraged that same foundation in TypeScript 2.1 to more deeply examine the type of any variable that seems like it’s destined for a better type. Instead of just choosing any<\/code>, TypeScript will infer types based on what you end up assigning later on.<\/p>\n
Let’s take the following example.<\/p>\n
\n
let<\/span> x;\n\n\/\/ We can still assign anything we want to 'x'.<\/span>\nx<\/span> =<\/span> () =><\/span> 42<\/span>;\n\n\/\/ After that last assignment, TypeScript 2.1 knows that 'x'<\/span>\n\/\/ has the type '() => number', so it can be called.<\/span>\nx<\/span>();\n\n\/\/ But now we'll get an error that we can't add a number to a function!<\/span>\nconsole<\/span>.log<\/span>(x<\/span> +<\/span> 42<\/span>);\n\/\/          ~~~~~~<\/span>\n\/\/ error: Operator '+' cannot be applied to types '() => number' and 'number'.<\/span>\n\n\/\/ TypeScript still allows us to assign anything we want to 'x'.<\/span>\nx<\/span> =<\/span> \"<\/span>Hello world!\"<\/span><\/span>;\n\n\/\/ But now it also knows that now 'x' is a 'string'!<\/span>\nx<\/span>.toLowerCase<\/span>();<\/pre>\n<\/div>\n
When it comes to assignments, TypeScript will still trust you and allow you to assign anything you want to x<\/code>. However, for any other uses, the type checker will know better by climbing up and looking at whatever you’ve actually done with x<\/code>.<\/p>\n
The same sort of tracking is now also done for empty arrays! This means better completions:<\/p>\n
\n
let<\/span> puppies =<\/span> [];\n\npuppies<\/span>.push<\/span>(new<\/span> Puppy<\/span>());\n\nfor<\/span> (let<\/span> pup of<\/span> puppies<\/span>) {\n    pup<\/span>.bark<\/span>();\n    \/\/  ^^^^ Get completion on 'bark'<\/span>\n}<\/pre>\n<\/div>\n
And it also means that TypeScript can catch more obvious errors:<\/p>\n
\n
puppies<\/span>[1<\/span>] =<\/span> new<\/span> Kitty<\/span>();\n\nfor<\/span> (let<\/span> pup of<\/span> puppies<\/span>) {\n    pup<\/span>.bark<\/span>();\n    \/\/  ~~~~ error: 'bark' does not exist on type 'Kitty'<\/span>\n}<\/pre>\n<\/div>\n
The end result of all this is that you’ll see way fewer<\/em> implicit any<\/code> errors in the future, and get much better tooling support.<\/p>\n
<\/a>Downlevel Async Functions<\/h2>\n
Support for down-level asynchronous functions (or async\/await) is coming in 2.1, and you can use it in today’s release candidate! async<\/code>\/await<\/code> is a new feature in ECMAScript 2017 that allows users to write code around promises without needing to use callbacks. async<\/code> functions can be written in a style that looks synchronous, but acts asynchronously, using the await<\/code> keyword.<\/p>\n
This feature was supported before TypeScript 2.1, but only when targeting ES6\/ES2015. TypeScript 2.1 brings the capability to ES3 and ES5 runtimes, meaning you’ll be free to take advantage of it no matter what environment you’re using.<\/p>\n
For example, let’s take the following function named delay<\/code>, which returns a promise and waits for a certain amount of time before resolving:<\/p>\n
\n
function<\/span> delay(milliseconds<\/span>:<\/span> number<\/span>) {\n    return<\/span> new<\/span> Promise<\/span><void<\/span>>(resolve<\/span> =><\/span> {\n      setTimeout<\/span>(resolve<\/span>, milliseconds<\/span>);\n    });\n}<\/pre>\n<\/div>\n
Let’s try to work on a simple-sounding task. We want to write a program that prints \"Hello\"<\/code>, three dots, and then \"World!\"<\/code>.<\/p>\n
\n
function<\/span> welcome() {\n    console<\/span>.log<\/span>(\"<\/span>Hello\"<\/span><\/span>);\n\n    for<\/span> (let<\/span> i =<\/span> 0<\/span>; i<\/span> <<\/span> 3<\/span>; i<\/span>++<\/span>) {\n        console<\/span>.log<\/span>(\"<\/span>.\"<\/span><\/span>);\n    }\n\n    console<\/span>.log<\/span>(\"<\/span>World!\"<\/span><\/span>);\n}<\/pre>\n<\/div>\n
This turned out to be about as simple as it sounded.<\/p>\n
Now let’s say we want to use our delay<\/code> function to pause before each dot.<\/p>\n
Without async<\/code>\/await<\/code>, we’d have to write something like the following:<\/p>\n
\n
function<\/span> dramaticWelcome() {\n    console<\/span>.log<\/span>(\"<\/span>Hello\"<\/span><\/span>);\n\n    (function<\/span> loop(i<\/span>){\n        if<\/span> (i<\/span> <<\/span> 3<\/span>) {\n            delay<\/span>(500<\/span>).then<\/span>(() =><\/span> {\n                console<\/span>.log<\/span>(\"<\/span>.\"<\/span><\/span>);\n                loop<\/span>(i<\/span> +<\/span> 1<\/span>);\n            });\n        }\n        else<\/span> {\n            console<\/span>.log<\/span>(\"<\/span>World!\"<\/span><\/span>);\n        }\n    })(0<\/span>);\n}<\/pre>\n<\/div>\n
This doesn’t look quite as simple any more! What about if we tried using async<\/code> functions to make this code more readable?<\/p>\n
First, we need to make sure our runtime has an ECMAScript-compliant Promise<\/code> available globally. That might involve grabbing a polyfill<\/a> for Promise<\/code>, or relying on one that you might have in the runtime that you’re targeting. We also need to make sure that TypeScript knows Promise<\/code> exists by setting our lib<\/code> flag to something like \"dom\", \"es2015\"<\/code> or \"dom\", \"es2015.promise\", \"es5\"<\/code>:<\/p>\n
\n
{\n    \"<\/span>compilerOptions\"<\/span><\/span>: {\n        \"<\/span>lib\"<\/span><\/span>: [\"<\/span>dom\"<\/span><\/span>, \"<\/span>es2015.promise\"<\/span><\/span>, \"<\/span>es5\"<\/span><\/span>]\n    }\n}<\/pre>\n<\/div>\n
Now we can rewrite our code to use async<\/code> and await<\/code>:<\/p>\n
\n
async<\/span> function<\/span> dramaticWelcome() {\n    console<\/span>.log<\/span>(\"<\/span>Hello\"<\/span><\/span>);\n\n    for<\/span> (let<\/span> i =<\/span> 0<\/span>; i<\/span> <<\/span> 3<\/span>; i<\/span>++<\/span>) {\n        await<\/span> delay<\/span>(500<\/span>);\n        console<\/span>.log<\/span>(\"<\/span>.\"<\/span><\/span>);\n    }\n\n    console<\/span>.log<\/span>(\"<\/span>World!\"<\/span><\/span>);\n}<\/pre>\n<\/div>\n
Notice how similar this is compared to our synchronous version! Despite its looks, this function is actually asynchronous<\/em>, and won’t block other code from running in between each pause. In fact, the two versions of dramaticWelcome<\/code> basically boil down to the same code, but with async<\/code> & await<\/code>, TypeScript does the heavy lifting for us.<\/p>\n
<\/a>Next Steps<\/h2>\n
TypeScript 2.1 RC has plenty of other features, and we’ll have even more coming for 2.1 proper. You can take a look at our roadmap<\/a> to see what else is in store. We hope you give it a try and enjoy it!<\/p>\n","protected":false},"excerpt":{"rendered":"
Today we’re happy to announce our release candidate for TypeScript 2.1! If you aren’t familiar with it, TypeScript is a language that adds optional static types to JavaScript, and brings new features from ES6 and later to whatever JavaScript runtime you’re using. As usual you can get the RC through NuGet, or just by running […]<\/p>\n","protected":false},"author":381,"featured_media":1797,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1679","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-typescript"],"acf":[],"blog_post_summary":"
Today we’re happy to announce our release candidate for TypeScript 2.1! If you aren’t familiar with it, TypeScript is a language that adds optional static types to JavaScript, and brings new features from ES6 and later to whatever JavaScript runtime you’re using. As usual you can get the RC through NuGet, or just by running […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts\/1679","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/users\/381"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/comments?post=1679"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts\/1679\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/media\/1797"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/media?parent=1679"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/categories?post=1679"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/tags?post=1679"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}