Task Tracker for this repo

[sakgoyal]

Is there a plan to make an issue tracker for things that are currently not implemented/broken?
It can be easier for contributors to know where to look for problems if there is a big specific list that people can "claim" so that work is not duplicated.

[RyanCavanaugh]

Is there a plan to make an issue tracker for things that are currently not implemented/broken?

I tried to do that in the README, not sure how better to communicate this. The issues list is not searchable for "works / doesn't work" kind of information IMO.

... that people can "claim"

We definitely are not expecting feature contributions from PRs at this point, so our internal work tracking for the team is the current source of truth on which features are being worked on. For actual bug bugs, the issue tracker exists

[jakebailey]

The simplest way is to find .diff files (that aren't just union ordering changes), and work from there.

Note that we do not do "claiming": https://github.com/microsoft/TypeScript/blob/main/CONTRIBUTING.md#issue-claiming

[sakgoyal]

that makes sense. I never thought of it that way.