provide additional justification for array interface design #35613
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
|
@bors: r+ rollup Thank you! |
|
📌 Commit a97ed61 has been approved by |
| @@ -269,13 +269,18 @@ mod prim_pointer { } | |||
| /// - `Borrow`, `BorrowMut` | |||
| /// - `Default` | |||
| /// | |||
| /// This limitation to `N in 0..32` exists because Rust does not yet support | |||
There was a problem hiding this comment.
Thanks! 👍
Fixed.
Explain why Rust does not implement traits for large arrays. Explain why most methods are implemented on slices rather than arrays.
matthew-piziak
force-pushed
the
array-docs-trait-justification
branch
from
a97ed61 to
e173ead
Compare
|
r? @peschkaj |
|
LGTM. 👍 |
|
@bors: r+ rollup |
|
📌 Commit e173ead has been approved by |
…tification, r=steveklabnik provide additional justification for array interface design Explain why Rust does not implement traits for large arrays. Explain why most methods are implemented on slices rather than arrays. Note: I'm dipping my toes in the water with a tiny PR. Especially looking for feedback on wording and style. Points of concern: appropriate level of top-level explanation; foreshadowing (is it appropriate to imply that we expect Rust's type system to eventually support size-generic arrays?); using `Foo` and `Bar` as type variables instead of e.g. `T` and `S`. @peschkaj
…tification, r=steveklabnik provide additional justification for array interface design Explain why Rust does not implement traits for large arrays. Explain why most methods are implemented on slices rather than arrays. Note: I'm dipping my toes in the water with a tiny PR. Especially looking for feedback on wording and style. Points of concern: appropriate level of top-level explanation; foreshadowing (is it appropriate to imply that we expect Rust's type system to eventually support size-generic arrays?); using `Foo` and `Bar` as type variables instead of e.g. `T` and `S`. @peschkaj
Explain why Rust does not implement traits for large arrays.
Explain why most methods are implemented on slices rather than arrays.
Note: I'm dipping my toes in the water with a tiny PR. Especially looking for feedback on wording and style. Points of concern: appropriate level of top-level explanation; foreshadowing (is it appropriate to imply that we expect Rust's type system to eventually support size-generic arrays?); using
FooandBaras type variables instead of e.g.TandS.@peschkaj