Rollup merge of #81665 - jacob-hughes:mir_doc_fix, r=estebank

Fix out of date `Scalar` documentation

Scalars can represent integers up to `u128`, but the docs state otherwise.
This commit is contained in:
Jack Huey 2021-02-02 16:01:49 -05:00 committed by GitHub
commit 70d16d506c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -96,7 +96,7 @@ pub fn from_machine_usize(i: u64, cx: &impl HasDataLayout) -> Self {
}
/// A `Scalar` represents an immediate, primitive value existing outside of a
/// `memory::Allocation`. It is in many ways like a small chunk of a `Allocation`, up to 8 bytes in
/// `memory::Allocation`. It is in many ways like a small chunk of a `Allocation`, up to 16 bytes in
/// size. Like a range of bytes in an `Allocation`, a `Scalar` can either represent the raw bytes
/// of a simple value or a pointer into another `Allocation`
#[derive(Clone, Copy, Eq, PartialEq, Ord, PartialOrd, TyEncodable, TyDecodable, Hash)]