I was about to follow this suggestion, but I think we really need to force the infos anyway for correctness: otherwise we might think two methods have the same name and issue a double-definition error in cases where one of them actually ends up with an expanded name due to the use of `makeNonPrivate`.