From d216d718bf545052d77968688861f83861a0225b Mon Sep 17 00:00:00 2001 From: Arnaud Date: Thu, 7 Jan 2021 12:18:25 +0100 Subject: Use `file_set::FileSet` and `FileSet` consistently in doc The first occurrence of `FileSet` has the full path (`file_set::FileSet`), while every other is simply `FileSet`. --- crates/vfs/src/lib.rs | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'crates/vfs') diff --git a/crates/vfs/src/lib.rs b/crates/vfs/src/lib.rs index 8c8d1114d..2b7b14524 100644 --- a/crates/vfs/src/lib.rs +++ b/crates/vfs/src/lib.rs @@ -18,15 +18,15 @@ //! free-form via list of globs, it's up to the [`Handle`] to interpret the globs //! in any specific way. //! -//! VFS stores a flat list of files. [`FileSet`] can partition this list of files -//! into disjoint sets of files. Traversal-like operations (including getting -//! the neighbor file by the relative path) are handled by the [`FileSet`]. +//! VFS stores a flat list of files. [`file_set::FileSet`] can partition this list +//! of files into disjoint sets of files. Traversal-like operations (including +//! getting the neighbor file by the relative path) are handled by the [`FileSet`]. //! [`FileSet`]s are also pushed to salsa and cause it to re-check `mod foo;` //! declarations when files are created or deleted. //! -//! [`file_set::FileSet`] and [`loader::Entry`] play similar, but different roles. +//! [`FileSet`] and [`loader::Entry`] play similar, but different roles. //! Both specify the "set of paths/files", one is geared towards file watching, -//! the other towards salsa changes. In particular, single [`file_set::FileSet`] +//! the other towards salsa changes. In particular, single [`FileSet`] //! may correspond to several [`loader::Entry`]. For example, a crate from //! crates.io which uses code generation would have two [`Entries`] -- for sources //! in `~/.cargo`, and for generated code in `./target/debug/build`. It will -- cgit v1.2.3