Unclear SetExpression with parameter behavior

Hi,

var interpreter = new Interpreter();
var parameter = new Parameter("x", typeof(int));
var expression = interpreter.Parse("x + 1", parameter).Expression;

var lambda = interpreter
    .SetExpression("value", expression)
    .Parse("value + 1", parameter);

var result = lambda.Invoke(1);

This will throw

System.InvalidOperationException: variable 'x' of type 'System.Int32' referenced from scope '', but it is not defined

Trying to register identifier like below leads to same exception

var lambda = interpreter
    .SetExpression("value", expression)
    .SetIdentifier(new Identifier("x", parameter.Expression)) 
    .Parse("value + 1", parameter);

And only if I mention the identifier in primary expression interpreter.Parse("x + value + 1", parameter) will parse with success.

Could you please advise how to propagate x parameter to internal expression without mentioning it in primary one?

Thanks

[metoule]

My bad, the parameter simply needs to be the same reference:

var interpreter = new ExpressionInterpreter();
var parameter = Expression.Parameter(typeof(int), "x");
var expression = interpreter.Parse("x + 1", parameter).Expression;

var lambda = interpreter
	.SetExpression("value", expression)
	.Parse("value + 1", parameter);

var result = lambda.Compile().DynamicInvoke(1);
Assert.AreEqual(3, result);

[metoule]

I like the proposal, but I think we should be careful so that the public interface remains as close as possible to the existing one so that users just have to recompile, but not have to update their code because it’s always painful.