SET: use the appropriate type while materializing
While materializing values in SET through the `OperationStack` we used to use as a type the type of the value associate to the currently used `BoundedValue`. This was wrong, this patch uses the type on the free operand on the top of the `OperationsStack` to perform the required computations.
Loading
Please register or sign in to comment