Ryan Cavanaugh

``` /// < reference types="./ReferencedTypes.d.ts" /> ``` I'm not sure how you got into a state where a relative `path` directive got updated to a `types` directive (I'm sure it's...

This issue is "awaiting more feedback". This means we'd like to hear from more people who would be helped by this feature, understand their use cases, and possibly contrast with...

All features incur risk and maintenance cost, especially the ones you think won't

[All features start at minus 100](https://gist.github.com/stuartd/a100fb315f2e5ca9ed17551d8b538a60); the *default* answer to any feature request is "no" in the absence of a strong case in favor of it. Looking into these features...

I think the root cause is that `Uppercase` and `Lowercase`, when given a widening literal type, give back a non-widening literal type. They could likely be changed to preserve the...

I don't think we should escape these unless there's some hard necessity.

Backlog = PRs accepted, be the change you want to see in the world 😇

We had some casual conversations about this and are basically terrified of how it would work in practice as soon as more than one person starts using it. What happens...

Yeah, I think a tsconfig-based mechanism is the thing that makes the most sense. The problem from there is figuring out the granularity. For "These defs are totally bad and...

You can use `// @ts-ignore`. Why are you intending to do this?