Flow vs TypeScript
Type Systems for JavaScript Flow and TypeScript http://djcordhose.github.io/flow-vs-typescript/flow-typescript-2.html Oliver Zeigermann / @DJCordhose More extensive version including Elm: http://bit.ly/js-types Part I: Introduction Why using type systems? type systems make code easier to maintain type annotations can make code more readable can make code easier to analyse can allow for reliable re
Checking React with Flow
ReactEurope 2016 Oliver Zeigermann / @DJCordhose djcordhose.github.io/react-intro-live-coding/2016_react_europe.html Flow is a static type checker, designed to quickly find errors in JavaScript applications Example #1: Simple Check with Type Inference const element = 'just a string'; // type is interred as string ReactDOM.render(element, mountNode); Message from flow src/step-1-typed/client/main.j
React with Flow
Bad // ERROR: Must be a ReactElement const element = 'just a string'; // type is interred as string ReactDOM.render(element, mountNode); Generics aka Parametric Types Consider this type hierarchy class Animal { name: string; constructor(name: string) { this.name = name; } } class Dog extends Animal { // just to make this different from cat goodBoyFactor: number; } class Cat extends Animal { purrFa
Flow vs TypeScript
Type Systems for JavaScript Oliver Zeigermann / @DJCordhose http://djcordhose.github.io/flow-vs-typescript/2016_hhjs.html Most recent version including TypeScript 2.0 can be found here (might be work in progress): http://djcordhose.github.io/flow-vs-typescript/flow-typescript-2.html Part I: Introduction Why using type systems? IMHO type systems make code easier to maintain type annotations can mak
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
