diff options
| author | bors <bors@rust-lang.org> | 2024-05-03 07:18:04 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-05-03 07:18:04 +0000 |
| commit | 1e7c467843bd1d0bcf8bfc27d057adacfa716da7 (patch) | |
| tree | 2aa1fcf2f2d920ca9407d2e6fc4bafa0ec8aa9aa /tests/codegen/patchable-function-entry/patchable-function-entry-both-flags.rs | |
| parent | b05f906a504c8ecfc5f9930508d79dac3ca25091 (diff) | |
| parent | d09331ce830bbae5953f02bd5b44f0076c998292 (diff) | |
| download | rust-1e7c467843bd1d0bcf8bfc27d057adacfa716da7.tar.gz rust-1e7c467843bd1d0bcf8bfc27d057adacfa716da7.zip | |
Auto merge of #17177 - hermannm:fix-run-lens-config, r=Veykril
Fix Run lens showing when lenses are disabled I have disabled Rust Analyzer lenses in my VSCode settings, but noticed that the `Run` lens still showed. This surprised me, as the docs for `lens.run.enable` [state that it only applies when `lens.enable` is set](https://github.com/rust-lang/rust-analyzer/blob/25f59be62f6b915b44a4c2ec2defca56a5f766c1/crates/rust-analyzer/src/config.rs#L353-L355). I then found that where we set `LensConfig::run`, we don't check `lens_enable` like for the other settings. [We did this previously](https://github.com/rust-lang/rust-analyzer/blob/eab385e1f64f8e3b861effe91432785f8030191b/crates/rust-analyzer/src/config.rs#L1649), so this seems like a regression from refactoring. This PR tries to fix that.
Diffstat (limited to 'tests/codegen/patchable-function-entry/patchable-function-entry-both-flags.rs')
0 files changed, 0 insertions, 0 deletions