I suggest we ...

Produce System.Linq.Expressions more efficiently

Most of .NET query providers are written in C# and use System.Linq.Expressions. While the conversion Expr->Expression is available it introduces significant penalty: http://stackoverflow.com/questions/32592811/why-is-f-expression-tree-generation-is-much-slower-than-c-can-it-be-made-fast

30 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Eugene Tolmachev shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

3 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Eugene Tolmachev commented  ·   ·  Flag as inappropriate

    Alternatively, maybe introduce an argument attribute, similar to ReflectedDefinition, something that would tell the compiler to produce C#-compatible tree from a lambda at compile-time, rather than the code to perform the conversion at runtime?

  • Dzmitry Lahoda commented  ·   ·  Flag as inappropriate

    Also I want want to use API of Elastic NEST or NHibernate I have to map F# Expr to Linq manually losing some readability of queries.

F# Language

Feedback and Knowledge Base