Piotr Osiewicz 5dc26c261d util: Use GlobSet in PathMatcher (#13197) ... Previously we were using a single globset::Glob in PathMatcher; higher up the stack, we were then resorting to using a list of PathMatchers. globset crate exposes a GlobSet type that's better suited for this use case. In my benchmarks, using a single PathMatcher with GlobSet instead of a Vec of PathMatchers with Globs is about 3 times faster with the default 'file_scan_exclusions' values. This slightly improves our project load time for projects with large # of files, as showcased in the following videos of loading a project with 100k source files. This project is *not* a git repository, so it should measure raw overhead on our side. Current nightly: 51404d4ea0 https://github.com/zed-industries/zed/assets/24362066/e0aa9f8c-aae6-4348-8d42-d20bd41fcd76 versus this PR: https://github.com/zed-industries/zed/assets/24362066/408dcab1-cee2-4c9e-a541-a31d14772dd7 Release Notes: - Improved performance in large worktrees		2024-06-18 16:12:24 +02:00
..
src	util: Use GlobSet in PathMatcher (#13197)	2024-06-18 16:12:24 +02:00
Cargo.toml	Refactor: Make it possible to share a remote worktree (#12775)	2024-06-07 12:53:01 -07:00
LICENSE-GPL	Rename 'project_core' crate to 'worktree', make it just about worktrees (#9189)	2024-03-11 11:35:27 -07:00