From c74fc1a1d9105307b2fe94372580ab667cefbbbb Mon Sep 17 00:00:00 2001 From: Max Lefebvre Date: Wed, 13 Nov 2019 21:57:20 -0400 Subject: [PATCH] update action-return-types.md (#14976) (#14983) --- aspnetcore/web-api/action-return-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/web-api/action-return-types.md b/aspnetcore/web-api/action-return-types.md index 4f08f6c39b..177480e8b4 100644 --- a/aspnetcore/web-api/action-return-types.md +++ b/aspnetcore/web-api/action-return-types.md @@ -44,7 +44,7 @@ When known conditions need to be accounted for in an action, multiple return pat ### Return IEnumerable\ or IAsyncEnumerable\ -In ASP.NET Core 2.2 and earlier, returning from an action results in synchronous collection iteration by the serializer. The result is the blocking of calls and a potential for thread pool starvation. To illustrate, imagine that Entity Framework (EF) Core is being used for the web API's data access needs. The following action's return type is synchronously enumerated during serialization: +In ASP.NET Core 2.2 and earlier, returning from an action results in synchronous collection iteration by the serializer. The result is the blocking of calls and a potential for thread pool starvation. To illustrate, imagine that Entity Framework (EF) Core is being used for the web API's data access needs. The following action's return type is synchronously enumerated during serialization: ```csharp public IEnumerable GetOnSaleProducts() =>