rustlings/exercises/primitive_types/README.md

# Primitive Types

Rust has a couple of basic types that are directly implemented into the
compiler. In this section, we'll go through the most important ones.

## Further information

- [Data Types](https://doc.rust-lang.org/stable/book/ch03-02-data-types.html)
- [The Slice Type](https://doc.rust-lang.org/stable/book/ch04-03-slices.html)
docs(exercises): updated all exercises readme files all exercises readme files now have a unified structure and a description 2021-04-23 12:54:31 -05:00			`# Primitive Types`
redo the section readmes 2019-01-23 14:02:06 -06:00
			`Rust has a couple of basic types that are directly implemented into the`
			`compiler. In this section, we'll go through the most important ones.`

docs(exercises): updated all exercises readme files all exercises readme files now have a unified structure and a description 2021-04-23 12:54:31 -05:00			`## Further information`
redo the section readmes 2019-01-23 14:02:06 -06:00
			`- [Data Types](https://doc.rust-lang.org/stable/book/ch03-02-data-types.html)`
fix(primitive_types4): Fail on a slice covering the wrong area 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. 2019-08-17 19:14:00 -05:00			`- [The Slice Type](https://doc.rust-lang.org/stable/book/ch04-03-slices.html)`