You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// method resolution is likely to hit all trait impls at some point
110
110
// we pre-populate it here as this will hit a lot of parses ...
111
-
_ = hir::TraitImpls::for_crate(&db, crate_id);
112
-
// we compute the lang items here as the work for them is also highly recursive and will be trigger by the module symbols query
111
+
// This also computes the lang items, which is what we want as the work for them is also highly recursive and will be trigger by the module symbols query
113
112
// slowing down leaf crate analysis tremendously as we go back to being blocked on a single thread
114
-
_ = hir::crate_lang_items(&db, crate_id);
113
+
_ = hir::TraitImpls::for_crate(&db, crate_id);
115
114
})
116
115
});
117
116
@@ -271,7 +270,6 @@ pub fn parallel_prime_caches(
271
270
}
272
271
273
272
if crate_def_maps_done == crate_def_maps_total {
274
-
// Can we trigger lru-eviction once at this point to reduce peak memory usage?
/// This config controls the frequency in which rust-analyzer will perform its internal Garbage
102
-
/// Collection. It is specified in revisions, roughly equivalent to number of changes. The default
103
-
/// is 1000.
104
-
///
105
-
/// Setting a smaller value may help limit peak memory usage at the expense of speed.
106
-
gc_frequency:usize = 1000,
107
-
108
101
/// If this is `true`, when "Goto Implementations" and in "Implementations" lens, are triggered on a `struct` or `enum` or `union`, we filter out trait implementations that originate from `derive`s above the type.
0 commit comments