diff options
| author | bors <bors@rust-lang.org> | 2019-04-22 01:50:48 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-04-22 01:50:48 +0000 |
| commit | e336d04c790e2d93f1a1d702cfeb68eb96744b2d (patch) | |
| tree | 4fc9e115213cd7e1707548b94e4f90e909f1e7da /src | |
| parent | 4b0b7093e5e0ba2c4b40509c9cb2541eb3a873fe (diff) | |
| parent | a71bc62c29cebec115700d98a61d618e0c7a83b9 (diff) | |
Auto merge of #144 - yvan-sraka:patch-0, r=komaeda
Add errors to exercises that compile without user changes
Hi !
I played a bit with rustlings, and I felt that some exercises were incorrect because they passed the tests without me needing to edit the files!
This gave me the feeling that the exercise was skiped! Especially when I use `rustlings watch`, it is easy to miss an exercise because the compilation error that is displayed is the one of the next exercise ...
It is easy to identify "broken" exercises with:
```bash
% find exercises -name "*.rs" | xargs -n 1 rustlings run
...
✅ Successfully ran exercises/move_semantics/move_semantics4.rs
✅ Successfully tested exercises/test2.rs
```
My suggestion is to make sure that these files trigger a compilation error by adding a simple syntax error (e.g. with `???` in the code that must change) so that our Rustacean can then play with it!
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions
