Hi there. First off, thank you for building this amazing library. I genuinely see it eventually becoming a de-facto standard for EF Core projects, it enables what I would consider essential functionality for EF Core, and does so in a way that's a lot more elegant than the likes of LINQKit. So, great job and keep up the brilliant work!
The README mentions that there are two compatibility modes, full and limited, and explains that the limited compatibility mode offers slightly better performance, presumably at the cost of being more limited in terms what the projectable property/method can contain, but it doesn't explain what exactly those limitations are. It would also be helpful if there was also an example of something that would work in the "full" mode and would fail in the "limited" mode.
Hi there. First off, thank you for building this amazing library. I genuinely see it eventually becoming a de-facto standard for EF Core projects, it enables what I would consider essential functionality for EF Core, and does so in a way that's a lot more elegant than the likes of LINQKit. So, great job and keep up the brilliant work!
The README mentions that there are two compatibility modes, full and limited, and explains that the limited compatibility mode offers slightly better performance, presumably at the cost of being more limited in terms what the projectable property/method can contain, but it doesn't explain what exactly those limitations are. It would also be helpful if there was also an example of something that would work in the "full" mode and would fail in the "limited" mode.
Thank you very much.