At the moment we statically add a kernel argument for the symbolic value dt no matter whether it is actually used in the form or not. On the other hand we never generate kernel parameters for any other symbolic values that may be used in forms.
With the current code structure this is slightly messy to implement, since the form expressions are analysed by ExpressionBuilder, whereas kernel parameters are generated by FormBackend. That means ExpressionBuilder.build will need to return a list of SymbolicValues used in the expression for which to generate kernel arguments.
At the moment we statically add a kernel argument for the symbolic value dt no matter whether it is actually used in the form or not. On the other hand we never generate kernel parameters for any other symbolic values that may be used in forms.
With the current code structure this is slightly messy to implement, since the form expressions are analysed by
ExpressionBuilder, whereas kernel parameters are generated byFormBackend. That meansExpressionBuilder.buildwill need to return a list ofSymbolicValues used in the expression for which to generate kernel arguments.