Clarify maximum pointer offset

gnzlbg · gnzlbg · commit 50d530ef7619 · 2019-04-15T14:40:30.000+02:00
diff --git a/reference/src/layout/scalars.md b/reference/src/layout/scalars.md
@@ -53,8 +53,8 @@ They have the same layout as the [pointer types] for which the pointee is
 >   usize]`. Only ZST arrays can probably be this large in practice, non-ZST
 >   arrays are bound by the maximum size of Rust values,
 >
-> * the maximum value by which a pointer can be offseted using `ptr.add(count:
->   usize)` is `usize::max_value()`.
+> * the maximum value in bytes by which a pointer can be offseted using
+>   `ptr.add` or `ptr.offset` is `isize::max_value()`.
 >
 > These limits have not gone through the RFC process and are not guaranteed to
 > hold.

Original file line number	Diff line number	Diff line change
`@@ -53,8 +53,8 @@ They have the same layout as the [pointer types] for which the pointee is`
`53`	`53`	> usize]`. Only ZST arrays can probably be this large in practice, non-ZST
`54`	`54`	`> arrays are bound by the maximum size of Rust values,`
`55`	`55`	`>`
`56`		-> * the maximum value by which a pointer can be offseted using `ptr.add(count:
`57`		-> usize)` is `usize::max_value()`.
	`56`	`+> * the maximum value in bytes by which a pointer can be offseted using`
	`57`	+> `ptr.add` or `ptr.offset` is `isize::max_value()`.
`58`	`58`	`>`
`59`	`59`	`> These limits have not gone through the RFC process and are not guaranteed to`
`60`	`60`	`> hold.`