Nested CallExpression causes System.AccessViolationException about fastexpressioncompiler

[dadhi]

But better no config at all )

[dadhi]

Thanks for the test! Will check.

May be we need to control supported expr types on the Client side, so that you may disable the culprit until fixed ?

[detoxhby]

Could you please explain the "Client side" scope you referred a bit more detailful in this context?

[dadhi]

By client I mean the general consumer of the FEC. Like to have a way to configure FEC:

ExpressionCompiler.Exclude(ExpressionType.MemberInit, other);

[detoxhby]

@dadhi seems like a good idea, but I would reverse it and exclude unsupported expressions by default with API support to include them.
This way FEC would always be safe and would allow future development to enable new features progressively as they become stable.

[dadhi]

We can have both :)