Serge Semenov

Yeah, it's very simple. Consider such case: ```csharp class Record { public Guid Id { get; set; } } class SampleDbContext { DbSet Records { get; set; } } ......

Probably a wrong place to discuss the architecture principle itself, but seems like this is the best thread on the entire internet about fundamental flaw of the onion architecture diagram...

Thanks for reporting this, @mhintzke, and it's a known issue. **Why It Happens.** The C# compiler generates a state machine similar to this: ```csharp class Test_StateMachine { Example __this; int...

yeah, why not. To my best memory, I added some core LINQ-style extension methods, but not all possible overloads.

@zivkan, thanks for the suggestion. You are absolutely right about the sequential producer pattern. This might not be obvious to everyone, however, there are many more standard types that don't...

P.S. I replied to the SO question as well: https://stackoverflow.com/questions/54402544/c-sharp-asyncenumerable-running-awaiting-multiple-tasks-never-finishes/56189780#56189780 I've been thinking about adding a helper method for such scenarios with concurrent producers/consumers.

Hi @Misiu , thanks for submitting the PR! Give me a few days to review this - have important things to do this week.

I would challenge you with such feature request and ask to think about using `CancellationToken` which is the recommended thing to use with asynchronous operations. Here is an example: ```csharp...

@JeffN825 , sorry for late reply as I was on my vacation. This library definitely has `SelectAsync` and `ToDictionaryAsync`, however, those built-in extension methods don't take in async delegates -...

Good try, but this is simply an unsupported scenario with concurrent producers. Imagine a synchronous version of the producer side: ```csharp IEnumerable Stream(...) { Parallel.ForEach(... => { yield return ...;...