Consistency with widths: int vs uint

[meowgorithm]

I've noticed, while using various parts Reflow together, that most packages int to describe widths, while the newer truncate package uses uint. For example:

// In the ansi sub-package
func PrintableRuneWidth(s string) int

// In the truncate sub-package
func String(s string, width uint) string

Why not standardize on or the other? If not breaking the API is a concern, then it would be safer to stay with int as the truncate package is still unreleased.