Well the resulting number contains more percision than the Int32 can hold, so I don't think this is a bug with the behavior, but rather a bug with the documentation.
↧