Flow vs. Typescript

Re:Flow vs. Typescript by joshuacc on Monday June 06, 2016 @09:47AM (#11846695)

That's not entirely accurate. TypeScript 1.8 added the ability to use type information from JSDoc-style comments.

For example:

    /**
     * @param {string} a
     * @param {number} b
     * @returns {string}
     */
    function foo(a, b){
      return a + b;
    }

Is functionally identical to:

    function foo(a: string, b: number): string {
      return a + b;
    }

See: https://github.com/Microsoft/TypeScript/issues/4790

[ Parent | on HN ]

Re:Flow vs. Typescript by Arnavion on Monday June 06, 2016 @01:49PM (#11848712)

Not equivalent - the TS compiler currently does not actually enforce the types in a JS file. See https://github.com/Microsoft/TypeScript/issues/4790#issuecom... The feature of parsing JSDoc comments is currently only used for providing completion info for JS editors and for consuming exported JS functions and variables in TS files.

[ Parent | on HN ]

Re:Flow vs. Typescript by joshuacc on Tuesday June 07, 2016 @03:32PM (#11857110)

Ah, you're right. Looks like I'd misunderstood the scope of that change.

[ Parent | on HN ]

Re:Flow vs. Typescript by abritinthebay on Monday June 06, 2016 @02:36PM (#11849111)

"functionally" identical to the type checker.

But not functionally identical when it involves my fingers typing (the function there being my ergonomics). Flow would just be inline comments at the code points required.

[ Parent | on HN ]