bartdesmet / expressionfutures Goto Github PK

The README says "More detailed information to follow...". It would be good if this can be updated with the current status of this work.

First of all I want to say thank you for your contribution.

I really like your idea to extend the expression tree generation with all the stuff you implemented.
But what I do not like is that it needs your custom roslyn-fork to do that. I would very much prefer I it would be implemented via CSharpSyntaxRewriter and could be used with regular roslyn / csc.

@bartdesmet
is this project in development or stopped? I watched on channel9 that you were referring to this project, but looking to the last commit, it is long ago?!

What are the plans to bring serialization for Expression trees? Do you have any timelines?

Rather than expanding Linq.Expressions I was considering minimizing it. I wrote a bit of experimental code, but ran into an issue/compilation error where assigning a c# lambda expression to an Expression ( a custom class in Language.Expressions ) resulted is a cs1660 error ( cannot convert lambda expression to type Expression because it is not a delegate type ). I was hoping that with your obvious expertise with Linq.Expressions you could help me out. Does the Rosyln compiler have internal knowledge of Linq.Expressions.Expression?

Any help would be appreciated. Thanks in advance.

Not sure whether this should go in this repo or your branch of rosyln, but I've been playing around with CSharpExpressions, and found a pretty simple limitation:

void main()
{
int num = 5;
Expression> expr = () => num++;
}

Causes csc.exe to crash in ExpressionLambdaRewriter.cs, in the function VisitLocal(BoundLocal node), trying to access a key in _localMap that doesn't exist for the captured symbol.

I'm gonna try to mess around with the ExpressionLambdaRewriter, but i'm not a compiler dev, so I'm gonna try to do my best.