diff options
| author | bors <bors@rust-lang.org> | 2019-08-18 08:24:44 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-08-18 08:24:44 +0000 |
| commit | c5bb32253b145b96c2f3049c2f0644f13d921290 (patch) | |
| tree | d256c711aa4c1a8a12a14b7122d755df37a52d16 /CONTRIBUTING.md | |
| parent | 2cd06826c0f4da8bc92825717e73eb44cd18095d (diff) | |
| parent | 5b1e673cec1658afc4ebbbc800213847804facf5 (diff) | |
Auto merge of #209 - Dylnuge:slice-assert, r=komaeda
fix(primitive_types4): Fail on a slice covering the wrong area
I noticed this issue and it seems like a similar one was raised/fixed in #160 this way. This is my first contribution to this repo (or any Rust project) so let me know if I messed up or need to fix anything!
---
This commit converts primitive_types4 to a test and asserts that the
slice given is equal to the expected slice.
The intent of the primitive_types4 exercise appears to be to ensure the
user understands inclusive and exclusive bounds as well as slice syntax.
`rustlings` commands using `compile` do not verify that a specific
println is reached and, in the case of `watch` and `verify` (but not
`run`), they do not output the `println`s at all.
This fix is semantically similar to #198. It does not take a stance on
the correct way to handle this for all exercises; see #127. There are
likely other exercises whose intent are masked by this issue.
Diffstat (limited to 'CONTRIBUTING.md')
0 files changed, 0 insertions, 0 deletions
