3 ms·
Worth bearing in mind that this only helps if you are using LINQ against in-memory objects (i.e. LINQ to Objects). Depending on how this detects IQueryable pro
by damieng 10y ago
Worth bearing in mind that this only helps if you are using LINQ against in-memory objects (i.e. LINQ to Objects). Depending on how this detects IQueryable providers it will either skip it, break it or worse of all silently 'work' but pull all the remote data into memory for evaluation. I'm hoping it's skip.
- matthewwarren 10y agoThis project only works with IEnumerable, not IQueryable, see https://github.com/antiufo/roslyn-linq-rewrite/blob/09216a3b2ab53474a93db861435c056523f194d0/RoslynLinqRewrite/RoslynLinqRewrite/LinqRewriter.Rules.cs#L167-L181 https://github.com/antiufo/roslyn-linq-rewrite/blob/09216a3b... for instance. I guess this is for exactly the reasons you talk about, i.e. once it's working with Expression tress too much is unknown and any optimisations would be v. risky.