Andrew Gallant 3b300559ab red_knot_python_semantic: remove #[must_use] on diagnostic guard constructor ... I believe this was an artifact of an older iteration of the diagnostic reporting API. But this is strictly not necessary now, and indeed, might even be annoying. It is okay, but perhaps looks a little odd, to do `builder.into_diagnostic("...")` if you don't want to add anything else to the diagnostic.		2025-04-22 12:08:03 -04:00
..
resources	[red-knot] Consider two instance types disjoint if the underlying classes have disjoint metaclasses (#17545)	2025-04-22 15:14:10 +01:00
src	red_knot_python_semantic: remove #[must_use] on diagnostic guard constructor	2025-04-22 12:08:03 -04:00
tests	[red-knot] Add GitHub PR annotations when mdtests fail in CI (#17150)	2025-04-02 21:51:52 +01:00
build.rs	Modernize build scripts (#13837)	2024-10-20 22:35:35 +01:00
Cargo.toml	[red-knot] Add a test to ensure that KnownClass::try_from_file_and_name() is kept up to date (#16326)	2025-02-24 12:14:20 +00:00
mdtest.py	mdtest.py: do a full mdtest run immediately when the script is executed (#17128)	2025-04-01 19:27:55 +01:00
mdtest.py.lock	[red-knot] Markdown test runner (#15632)	2025-01-21 14:06:35 +01:00