language-servers/ruff
1
0
Fork 0
mirror of https://github.com/astral-sh/ruff.git synced 2025-09-29 13:25:17 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

[red-knot] Use type[Unknown] rather than Unknown as the fallback metaclass for invalid classes (#14961)

Browse source
This commit is contained in:
Alex Waygood 2024-12-13 19:48:51 +00:00 • committed by GitHub
parent 4b2b126b9f
commit 90a5439791
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 8 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

10
crates/red_knot_python_semantic/src/types.rs
View file

@ -2925,10 +2925,10 @@ impl<'db> Class<'db> {
Some(metaclass_ty)
}
/// Return the metaclass of this class, or `Unknown` if the metaclass cannot be inferred.
/// Return the metaclass of this class, or `type[Unknown]` if the metaclass cannot be inferred.
pub(crate) fn metaclass(self, db: &'db dyn Db) -> Type<'db> {
// TODO: `type[Unknown]` would be a more precise fallback
self.try_metaclass(db).unwrap_or(Type::Unknown)
self.try_metaclass(db)
.unwrap_or_else(|_| Type::subclass_of_base(ClassBase::Unknown))
}
/// Return the metaclass of this class, or an error if the metaclass cannot be inferred.
@ -2941,9 +2941,7 @@ impl<'db> Class<'db> {
// We emit diagnostics for cyclic class definitions elsewhere.
// Avoid attempting to infer the metaclass if the class is cyclically defined:
// it would be easy to enter an infinite loop.
//
// TODO: `type[Unknown]` might be better here?
return Ok(Type::Unknown);
return Ok(Type::subclass_of_base(ClassBase::Unknown));
}
let explicit_metaclass = self.explicit_metaclass(db);