Update primitives.md

[daniel-web-developer]

Since tuples can hold values of different types, I think it would be important to make it obvious they can do so.

Right now, the book is saying "Tuples like (1, true).". This might make the impression that tuples are limited to holding values of the same type, so that's why I'm proposing to change 1 to a 2, making it "Tuples like (2, true).".

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @marioidival (or someone else) soon.

[AndreasHuber]

1 and true are of different types, i32 and bool respectively, but 2 is an i32 just like 1. Thus, the proposal presents no meaningful change to the example and I would suggest closing this PR.

[daniel-web-developer]

1 and true are of different types, i32 and bool respectively, but 2 is an i32 just like 1. Thus, the proposal presents no meaningful change to the example and I would suggest closing this PR.

They're different types, but as a beginner in Rust, I couldn't tell that at first. The change I'm proposing would save other beginners from the same confusion (since true can be represented as 1 in lots of other languages).

[marioidival]

I think the best decision here is closing the PR because in the same page we are introducing to the users to the scalar types in Rust:

# Primitives
Rust provides access to a wide variety of `primitives`. A sample includes:
### Scalar Types
* Signed integers: `i8`, `i16`, `i32`, `i64`, `i128` and `isize` (pointer size)
* Unsigned integers: `u8`, `u16`, `u32`, `u64`, `u128` and `usize` (pointer
  size)
* Floating point: `f32`, `f64`
* `char` Unicode scalar values like `'a'`, `'α'` and `'∞'` (4 bytes each)
* `bool` either `true` or `false`
* The unit type `()`, whose only possible value is an empty tuple: `()`