This pull request was generated by the VS Perf Rel AI Agent. Please review this AI-generated PR with extra care! For more information, visit our wiki. Please share feedback with TIP Insights

• Issue: The allocation hot path is TypeAllocated!NuGet.LibraryModel.LibraryDependency[] with frames showing List<T>.EnsureCapacity/set_Capacity, which indicates repeated List backing-array growth.
  In DependencyGraphResolver.DependencyGraphItem.cs, method DependencyGraphResolver.DependencyGraphItem.GetGraphItemAsync, the new list is created with an incorrect capacity due to operator precedence:

new(capacity: RuntimeDependencies?.Count ?? 0 + item.Data.Dependencies.Count)

Because + binds tighter than ??, when RuntimeDependencies is non-null the capacity becomes just RuntimeDependencies.Count (ignoring item.Data.Dependencies.Count), causing predictable resizing and LibraryDependency[] allocations as items are added.

• Issue type: Specify an up-front capacity for collections if one is known
• Proposed fix: Fixing the expression to new(capacity: (RuntimeDependencies?.Count ?? 0) + item.Data.Dependencies.Count) is a trivial, localized change with minimal risk and directly addresses the hot-path allocations.

Best practices wiki
See related failure in PRISM
ADO work item