How do you feel about setting maxBytes to uint64 rather than int?

[asoorm]

https://github.com/globalsign/mgo/blob/master/session.go#L2925

This way if we want capped collections, we don't have the restriction of deployment of this driver to a 64bit machine

[domodwyer]

Hi @asoorm

Using an int where the correct type should be a uint is something that annoys me more than it should! However in the interests of backwards compatibility I'm of the opinion we should leave it as is.

Lets be clear - I completely agree with you, it's an obvious mistake in the original implementation, but changing it would mean users can't use our fork as a drop-in replacement for mgo. If we ever break this compatibility, I'll be changing this to a uint64 for sure.

Dom