Skip to content

[red-knot] Create red-knot-python-semantic crate #11920

@MichaReiser

Description

@MichaReiser

I know I said this morning I was OK either way, but after reading this PR and thinking about it more, I really do favor putting all this in a separate crate. I don't see any shared code between the old ruff_python_semantic code and the new, and looking through the old semantic model code, I'm not really seeing where there would be shared code between them in the future (or even any direct dependency between them). I think the code we are likely to share is in other crates; ruff_python_semantic we are basically replacing. I think it will be a lot clearer, both for maintainers of the old semantic model and for development of the new, if we use a new crate.

_Originally posted by @carljm in #11860 (comment)

Metadata

Metadata

Assignees

Labels

tyMulti-file analysis & type inference

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions