Brent Westbrook 92ecfc908b [syntax-errors] Make async-comprehension-in-sync-comprehension more specific (#17460) ... ## Summary While adding semantic error support to red-knot, I noticed duplicate diagnostics for code like this: ```py # error: [invalid-syntax] "cannot use an asynchronous comprehension outside of an asynchronous function on Python 3.9 (syntax was added in 3.11)" # error: [invalid-syntax] "`asynchronous comprehension` outside of an asynchronous function" [reveal_type(x) async for x in AsyncIterable()] ``` Beyond the duplication, the first error message doesn't make much sense because this syntax is _not_ allowed on Python 3.11 either. To fix this, this PR renames the `async-comprehension-outside-async-function` semantic syntax error to `async-comprehension-in-sync-comprehension` and fixes the rule to avoid applying outside of sync comprehensions at all. ## Test Plan New linter test demonstrating the false positive. The mdtests from my red-knot PR also reflect this change.		2025-04-24 15:45:54 -04:00
..
snapshots	[syntax-errors] Make async-comprehension-in-sync-comprehension more specific (#17460)	2025-04-24 15:45:54 -04:00
fixtures.rs	[red-knot] Detect semantic syntax errors (#17463)	2025-04-23 09:52:58 -04:00
generate_inline_tests.rs	[syntax-errors] Start detecting compile-time syntax errors (#16106)	2025-03-21 14:45:25 -04:00