> I think this is an artefact of the long-gone days before MLton > supported overflow. It seems fine to replace as you suggest. In fact, since the IntInf implementation has not been substantially revised since those days, it probably has a number of similar artefacts that would benefit from rewriting to take advantage of overflow.