Red Knot Contributions

[Slyces]

Hi guys, first off, congratulation on the awesome work you've been doing.
I have seen that ruff is currently working on type checking capabilities with red-knot.
Do you guys welcome contributions to this project, even on very minor issues?
I'd love to do what I can to make this happen sooner 😄

[MichaReiser]

Hi @Slyces and awesome that you're interested in contributing.

Contributing is a bit hard at the moment because we have yet to figure out the fundamental architecture fully. That means there's a lot of change in direction, unstable APIs, merge conflicts. Coordination is a challenge right now. That's why we aren't currently looking for external contributors (we haven't onboarded the entire team for the very same reason).

I would be very interested in external contributions once we reach a step where things feel "stable enough" and where we also have work that isn't on the critical path, where having it a day or two later immediately becomes a blocker for the team. Give us another 4 weeks and we hopefully have most figured (there will still be ton of work!) out by then.

[MichaReiser]

Thanks for the ping! I wanted to post an update but forgot. I'm sorry.

You can use this view to see all red-knot issues. There's at least one that's currently marked as help wanted and there are a few bugs that might not be too hard. We plan to create more good first issues/help wanted issues in the near time.

[ewilazarus]

Hey, I'd like to ask if this is already usable? Are there any docs?

(Sorry if this is not the right thread)

[purepani]

Afaik, no it is not.
Its still very early in development

[winwinashwin]

Hi, I would like to do some early experiments with red-knot-wasm. Is red-knot currently in a usable state to test things out?

[MichaReiser]

No, not yet. There will be an official announcement when it is, but I suspect that it will take even longer before the WASM api becomes stable (it's mainly for internal use)