Ryan Cavanaugh comments

Results 457 comments of


                                            Ryan Cavanaugh

Make function properties context-sensitive based on their return statements

Related -- #47599

Make function properties context-sensitive based on their return statements

@typescript-bot pack this

Make function properties context-sensitive based on their return statements

@weswigham @ahejlsberg I remember from prior conversations that this approach is maybe not *quite* right (due to CFA in function bodies?), but I wasn't able to craft a demonstration of...

feat: @types/acorn and @types/acorn-walk

This is a very odd situation; types do not normally come *back* into DT. @marijnh is this PR what you were intending to happen?

fix(flatry): Adds type never

My prior review stands; a tuple containing a nonoptional `never` element doesn't make sense.

fix(flatry): Adds type never

Right, the Playground link shows why this code is wrong. You can't legally call this function with an error value: ```ts const testB = (b: FlatryB) => { const [err,...

fix(flatry): Adds type never

The kind of narrowing you'd need here isn't supported by TypeScript yet. The code *also* claims to return `string` even without the check: ```ts // Marked as returning string, but...

Mixins not working as expected for generic types

Please give *concrete* expected / actual behaviors. I can't know what you expect to happen, or why, based on these descriptions.

"import type { X }" with exported value with same name gives "Individual declarations in merged declaration 'X' must be all exported or all local."

The error is exactly describing the situation that's happening. You can write ```ts import type { x } from './foo'; const x = 7 export { x }; ```

Allow multiple tsconfig configurations for `--project` flag in cli

Apart from pure startup time, there's not anything meaningful that can be reused between two subsequent project builds. It might actually be worse from a total time perspective because of...