Alex Zaytsev

This was implemented in f817b79f91f9ba046eee88070ddec22f5c214592 but then commit has disappeared and I'm struggling to find where it has gone.

It seems like this is the regression of following: https://github.com/nhibernate/nhibernate-core/commit/a35aaa648b2cbd936a6a514357e8a538d74206be

Additional details in #2427

We can start using C# 8 now and add support of the interface in the current version. The interfaces are available in the compatibility package. To be able to do...

The only problem I see now: we need a support from @maca88’s AsyncGenerator so we can start using the new C#8 syntactic sugar

> By adding Microsoft.Bcl.AsyncInterfaces we do not gain the ability to use C#8 syntactic sugars like await foreach Obviously not. What I mean is that we need AsyncGenerator support to...

Note for future implementors: The likely query generated from the Linq in question should be similar to this: ```sql SELECT p.Id personId, d.Id dogId, d.Name dogName, c.Id catId, c.Name catName...

@chengang-hub this is too old, unfortunately we would not be able to fix it in 4.x branch. I would advise you to upgrade.

> Similarly to https://github.com/nhibernate/nhibernate-core/pull/3000 will cause intermittent (quite often) failure builds like https://github.com/nhibernate/nhibernate-core/pull/3000#issuecomment-1016601861 I've set maxcpucount to 1, so it should help. However, builds might become slower.

> However, builds might become slower. Seems the same time.