5 ms·

I'll rephrase. Does LINQ's map come with a plethora of problems like I'm told Task's map does above? Should you avoid mapping because 'it's the old callback m

• pjc50 3y ago
  Mapping (spelt "Select" quite often in LINQ) is entirely normal and promoted going forwards. It can optimize extremely well for simple cases. By default it is not parallel and compiles to an underlying for loop. Or you can use it with Tasks. https://itnext.io/fun-csharp-doing-linq-to-tasks-because-task-is-a-monad-2fd87a310a03 https://itnext.io/fun-csharp-doing-linq-to-tasks-because-tas... (caution: contains the M word) More from Microsoft: https://devblogs.microsoft.com/pfxteam/tasks-monads-and-linq/ https://devblogs.microsoft.com/pfxteam/tasks-monads-and-linq... ; referencing Lippert https://ericlippert.com/category/monads/ https://ericlippert.com/category/monads/ ContinueWith is not a broken "map". What people usually want is Select. https://learn.microsoft.com/en-us/dotnet/csharp/linq/standard-query-operators/projection-operations https://learn.microsoft.com/en-us/dotnet/csharp/linq/standar...