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
Given that we already have ToLambaExpression and after #271 we will have ToLightExpression.
Now we have possibility to convert the Light Expression from and to the System Expression.
The missing link is the ability to compare the restored expression.
This issue should address it.
Update
For now, we may compare the expressions converted to the C# code (which is not optimal):
#if LIGHT_EXPRESSIONvarsysExpr=expr.ToLambdaExpression();varrestoredExpr=sysExpr.ToLightExpression();// todo: @feature #431 compare the restored target and source expressions directly instead of stringsAssert.AreEqual(expr.ToCSharpString(),restoredExpr.ToCSharpString());
#endif
Update:
Take into account that when comparing the generated C# code, the generated names may be different based on the new expression identities. Because currently AppendName provides the unique name suffix based on the expression.GetHashCode()
The text was updated successfully, but these errors were encountered:
Given that we already have
ToLambaExpression
and after #271 we will haveToLightExpression
.Now we have possibility to convert the Light Expression from and to the System Expression.
The missing link is the ability to compare the restored expression.
This issue should address it.
Update
For now, we may compare the expressions converted to the C# code (which is not optimal):
Update:
Take into account that when comparing the generated C# code, the generated names may be different based on the new expression identities. Because currently
AppendName
provides the unique name suffix based on theexpression.GetHashCode()
The text was updated successfully, but these errors were encountered: