History

Dylan 74f64d3f96 Server: Allow `FixAll` action in presence of version-specific syntax errors (#16848 ) The single flag `has_syntax_error` on `LinterResult` is replaced with two (private) flags: `has_valid_syntax` and `has_no_unsupported_syntax_errors`, which record whether there are `ParseError`s or `UnsupportedSyntaxError`s, respectively. Only the former is used to prevent a `FixAll` action. An attempt has been made to make consistent the usage of the phrases "valid syntax" (which seems to be used to refer only to _parser_ errors) and "syntax error" (which refers to both _parser_ errors and version-specific syntax errors). Closes #16841		2025-03-20 05:09:14 -05:00
..
benches	Server: Allow `FixAll` action in presence of version-specific syntax errors (#16848 )	2025-03-20 05:09:14 -05:00
resources	Vendor benchmark test files (#15878 )	2025-02-02 18:16:07 +00:00
src	Vendor benchmark test files (#15878 )	2025-02-02 18:16:07 +00:00
Cargo.toml	Move `red_knot_python_semantic::PythonVersion` to the `ruff_python_ast` crate (#16147 )	2025-02-14 12:48:08 -05:00
README.md	Update contributing docs to use `cargo bench -p ruff_benchmark` (#9535 )	2024-01-15 14:57:30 -05:00

README.md

Ruff Benchmarks

The ruff_benchmark crate benchmarks the linter and the formatter on individual files:

# Run once on the "baseline".
cargo bench -p ruff_benchmark -- --save-baseline=main

# Compare against the "baseline".
cargo bench -p ruff_benchmark -- --baseline=main

# Run the lexer benchmarks.
cargo bench -p ruff_benchmark lexer -- --baseline=main

See CONTRIBUTING.md on how to use these benchmarks.