docs(perf): clarify Map-based resolver optimization applies since v3.0.0 in all docs

This commit is contained in:
Sergey Penkovsky
2025-08-06 08:29:00 +03:00
parent 52a55219ab
commit 05cfca5977
3 changed files with 3 additions and 3 deletions

View File

@@ -97,7 +97,7 @@ final dataBloc = await subScope.resolveAsync<DataBloc>();
### Fast Dependency Lookup (Performance Improvement)
> **Performance Note:**
> As of the latest version, CherryPick uses a Map-based resolver index for dependency lookup. This means calls to `resolve<T>()` and related methods are now O(1) operations, regardless of the number of modules or bindings in your scope. Previously, the library had to iterate over all modules and bindings to locate the requested dependency, which could impact performance as your project grew.
> **Starting from version 3.0.0**, CherryPick uses a Map-based resolver index for dependency lookup. This means calls to `resolve<T>()` and related methods are now O(1) operations, regardless of the number of modules or bindings in your scope. Previously, the library had to iterate over all modules and bindings to locate the requested dependency, which could impact performance as your project grew.
>
> This optimization is internal and does not change any library APIs or usage patterns, but it significantly improves resolution speed in larger applications.