about summary refs log tree commit diff
path: root/src/rustllvm/RustWrapper.cpp
diff options
context:
space:
mode:
authorJonathan Turner <jonathandturner@users.noreply.github.com>2016-08-17 06:25:24 -0700
committerGitHub <noreply@github.com>2016-08-17 06:25:24 -0700
commit559bfd68e36eb1328970a803f87049bdde285d7f (patch)
treea377a112c33262c8532f8972f752653aca642876 /src/rustllvm/RustWrapper.cpp
parent997a248c017db838093ddfb06654028721129bfd (diff)
parente173ead68458da5c4cb241f3d105abc87c529071 (diff)
downloadrust-559bfd68e36eb1328970a803f87049bdde285d7f.tar.gz
rust-559bfd68e36eb1328970a803f87049bdde285d7f.zip
Rollup merge of #35613 - matthew-piziak:array-docs-trait-justification, 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
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions