You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This library is not quite fulfilling the full promise of LINQ. LINQ supports in-memory collections as well as query providers via expressions.
In the case of the methods that operate on in-memory collections, that is, those methods that extend IEnumerable, the returned enumerable object captures the arguments that were passed to the method. When that object is enumerated, the logic of the query operator is employed and the query results are returned.
In contrast, methods that extend IQueryable do not implement any querying behavior, but build an expression tree that represents the query to be performed. The query processing is handled by the source IQueryable object.
Hopefully that didn't come off sounding like an insult, because I think this library is extremely 🆒 ! I'm curious if there is planned work or an interest to port support for query provider(s)? It's a huge undertaking, but since Microsoft open-sourced EntityFramework 6 & Core (which uses re-linq) and there's a JavaScript parser (i.e., expression generator) written in JavaScript, it's definitely possible…
The text was updated successfully, but these errors were encountered:
This library is not quite fulfilling the full promise of LINQ. LINQ supports in-memory collections as well as query providers via expressions.
Hopefully that didn't come off sounding like an insult, because I think this library is extremely 🆒 ! I'm curious if there is planned work or an interest to port support for query provider(s)? It's a huge undertaking, but since Microsoft open-sourced EntityFramework 6 & Core (which uses re-linq) and there's a JavaScript parser (i.e., expression generator) written in JavaScript, it's definitely possible…
The text was updated successfully, but these errors were encountered: