Exact

Exact Union RegExp

Dylan b6bd32d9dc Track t-strings and f-strings for token-based rules and suppression comments (#20357) ... Our token-based rules and `noqa` extraction used an `Indexer` that kept track of f-string ranges but not t-strings. We've updated the `Indexer` and downstream uses thereof to handle both f-strings and t-strings. Most of the diff is renaming and adding tests. Note that much of the "new" logic gets to be naive because the lexer has already ensured that f and t-string "starts" are paired with their respective "ends", even amidst nesting and so on. Finally: one could imagine wanting to know if a given interpolated string range corresponds to an f-string or a t-string, but I didn't find a place where we actually needed this. Closes #20310		2025-09-12 13:00:12 -05:00
..
indexer.rs	Track t-strings and f-strings for token-based rules and suppression comments (#20357)	2025-09-12 13:00:12 -05:00
interpolated_string_ranges.rs	Track t-strings and f-strings for token-based rules and suppression comments (#20357)	2025-09-12 13:00:12 -05:00
lib.rs	Track t-strings and f-strings for token-based rules and suppression comments (#20357)	2025-09-12 13:00:12 -05:00
multiline_ranges.rs	Maintain synchronicity between the lexer and the parser (#11457)	2024-06-03 18:23:50 +05:30