summaryrefslogtreecommitdiff
path: root/info.toml
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2019-08-18 08:24:44 +0000
committerbors <bors@rust-lang.org>2019-08-18 08:24:44 +0000
commitc5bb32253b145b96c2f3049c2f0644f13d921290 (patch)
treed256c711aa4c1a8a12a14b7122d755df37a52d16 /info.toml
parent2cd06826c0f4da8bc92825717e73eb44cd18095d (diff)
parent5b1e673cec1658afc4ebbbc800213847804facf5 (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 'info.toml')
-rw-r--r--info.toml2
1 files changed, 1 insertions, 1 deletions
diff --git a/info.toml b/info.toml
index d7f86f9..08114de 100644
--- a/info.toml
+++ b/info.toml
@@ -66,7 +66,7 @@ mode = "compile"
[[exercises]]
path = "exercises/primitive_types/primitive_types4.rs"
-mode = "compile"
+mode = "test"
[[exercises]]
path = "exercises/primitive_types/primitive_types5.rs"