No, because the 'normalization' is not an error. To simplify the logic, computations are done on a dinteger_t, then 'normalized' down to match the type. This is the way it has always worked. The method is not incorrect, it just moves all the normalization to IntegerExp itself rather than spreading it around.