mirror of https://github.com/astral-sh/ruff
red_knot_python_semantic: remove comment about `TypeCheckDiagnostic`
I put this in its own commit in case all of the information removed here was controversial. But it *looks* stale to me. At the very least, `TypeCheckDiagnostic` no longer exists, so that would need to be fixed. And it doesn't really make sense to me (at this point) to make `Diagnostic` a Salsa struct, particularly since we are keen on using it in Ruff (at some point).
This commit is contained in:
parent
c30e80a3f4
commit
185bcfef1a
|
|
@ -895,12 +895,6 @@ declare_lint! {
|
||||||
}
|
}
|
||||||
|
|
||||||
/// A collection of type check diagnostics.
|
/// A collection of type check diagnostics.
|
||||||
///
|
|
||||||
/// The diagnostics are wrapped in an `Arc` because they need to be cloned multiple times
|
|
||||||
/// when going from `infer_expression` to `check_file`. We could consider
|
|
||||||
/// making [`TypeCheckDiagnostic`] a Salsa struct to have them Arena-allocated (once the Tables refactor is done).
|
|
||||||
/// Using Salsa struct does have the downside that it leaks the Salsa dependency into diagnostics and
|
|
||||||
/// each Salsa-struct comes with an overhead.
|
|
||||||
#[derive(Default, Eq, PartialEq)]
|
#[derive(Default, Eq, PartialEq)]
|
||||||
pub struct TypeCheckDiagnostics {
|
pub struct TypeCheckDiagnostics {
|
||||||
diagnostics: Vec<Diagnostic>,
|
diagnostics: Vec<Diagnostic>,
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue