Skip to content

perf(engine): avoid closure allocation in AfterHookPairTracker.GetOrCreateAfterAssemblyTask (#6041) #6071

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thomhurst merged 1 commit into from
May 28, 2026
Merged

perf(engine): avoid closure allocation in AfterHookPairTracker.GetOrCreateAfterAssemblyTask (#6041) #6071

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions TUnit.Engine/Services/AfterHookPairTracker.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,6 +155,12 @@ public ValueTask<List<Exception>> GetOrCreateAfterTestSessionTask(Func<ValueTask
/// </summary>
public ValueTask<List<Exception>> GetOrCreateAfterAssemblyTask(Assembly assembly, Func<Assembly, ValueTask<List<Exception>>> taskFactory)
{
// Lock-free fast path avoids allocating a closure on the common cache-hit case.
if (_afterAssemblyTasks.TryGetValue(assembly, out var existingTask))
{
return new ValueTask<List<Exception>>(existingTask);
}

var task = _afterAssemblyTasks.GetOrAdd(assembly, a => taskFactory(a).AsTask());
return new ValueTask<List<Exception>>(task);
}
Expand Down
Loading