diff options
| author | bors <bors@rust-lang.org> | 2024-04-18 07:38:32 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-04-18 07:38:32 +0000 |
| commit | 062e1b9b81542680afde1aa47fa5316ac5133461 (patch) | |
| tree | fe9115d2f550701e1475f99c2c2ec8e48b8107cb /tests/ui/patchable-function-entry/patchable-function-entry-flags.rs | |
| parent | 46702ffc1a02a2ac153f1d1ce619ec917af8f3a6 (diff) | |
| parent | bd133eecdaed3bc72f35bd87e72bd540a666e84d (diff) | |
| download | rust-062e1b9b81542680afde1aa47fa5316ac5133461.tar.gz rust-062e1b9b81542680afde1aa47fa5316ac5133461.zip | |
Auto merge of #17093 - Wilfred:vfs_ignore_symlink_cycles, r=Veykril
fix: VFS should not walk circular symlinks As of #6246, rust-analyzer follows symlinks. This can introduce an infinite loop if symlinks point to parent directories. Considering that #6246 was added in 2020 without many bug reports, this is clearly a rare occurrence. However, I am observing rust-analyzer hang on projects that have symlinks of the form: ``` test/a_symlink -> ../../ ``` Ignore symlinks that only point to the parent directories, as this is more robust but still allows typical symlink usage patterns.
Diffstat (limited to 'tests/ui/patchable-function-entry/patchable-function-entry-flags.rs')
0 files changed, 0 insertions, 0 deletions