Function getWidth(width){\n\u3000return num + 3\n}<\/code><\/pre>\n\n\n\nHere, the type of variable width is not known. If I call this with, getWidth(\u201cI love TS\u201d) it will print I love TS3. This is known as type coercion. If it can, Javascript will see that it is trying to add a string and a number together, and it will convert the number to its string equivalent and concatenate them.<\/p>\n\n\n\n
With TypeScript, I could do the following:<\/p>\n\n\n\n
function getWidth(width: number) {\n return num + \uff13\n}<\/code><\/pre>\n\n\n\nWe just added the type of variable width as a number<\/code>. If I call add(\u201cI love TS\u201d)<\/code> now, it\u2019ll throw a compilation error \u2014 Argument of type <\/strong>string<\/strong><\/code> is not assignable to parameter of type <\/strong>number<\/strong><\/code> .<\/p>\n\n\n\nCatching the error instantly allows me to save time and check why my input is not the type I think it is, rather than having to trace my steps back much later in the process without being sure where the error is occurring.<\/p>\n\n\n\n
Benefits of Static Typing<\/p>\n\n\n\n
- TypeScript is that it offers the ability to add static types to your JavaScript code. <\/li>
- Static typing allows you to catch errors earlier in the debugging process.<\/li>
- Adding strict types makes code more readable. A code that speaks for itself can offset the lack of direct communication between team members.<\/li><\/ul>\n\n\n\n
By Ami<\/p>\n
\n <\/g:plusone><\/div>\n
![\"\u3053\u306e\u30a8\u30f3\u30c8\u30ea\u30fc\u3092\u306f\u3066\u306a\u30d6\u30c3\u30af\u30de\u30fc\u30af\u306b\u8ffd\u52a0\"](\"\/\/b.hatena.ne.jp\/images\/entry-button\/button-only@2x.png\")
<\/a>