Would like to contribute if accepted

Thanks for raising this issue.

Use of unsigned would seem to make sense as you point out, but unless I am misreading the code, making such a change would wind up breaking the Go compatibility guarantee, set out in https://golang.org/doc/go1compat.

@bradfitz @kardianos

@thanm Yes. Updating existing fields wouldn't be feasible, we may introduce new properties though.

In general Go prefers to use signed integers for numeric values, even if those values can never be negative.

This is because computer arithmetic, as compared to ordinary arithmetic, always has strange behaviors at some point. For signed types the strange behavior is at very large or very small values. For unsigned types the strange behavior is at zero. In practice numbers close to 0 are much much more common than numbers that are very large or very small. So it's better to use signed types.

Closing because we can't make this change in any case, as it would break the compatibility guidelines.