I have been thinking about the fast integer types:

`int_fast8_t`, `int_fast16_t`, `int_fast32_t`, `int_fast64_t`, `uint_fast8_t`, `uint_fast16_t`, `uint_fast32_t`, `uint_fast64_t`

over the last days and I asked a question about *why* (if so) these types are faster than the other integer types: 

[Why are the fast integer types faster than the other integer types?](https://stackoverflow.com/questions/59593541/why-are-the-fast-integer-types-faster-than-the-other-integer-types)

---

Something I have further thought about now is, **if**:

1. Faster types *are* faster on a certain environment (implementation/architecture-dependent) and thus that environment reflects an ideal environment for this question,
2. Objects with the class of `register` *are* stored inside a register of the CPU (but in general do not always need to be stored there when declared with the `register` class), they are faster on the same environment, and
3. A register of the CPU is capable of holding the required integer value,

---

	* Are the fast integer types even \*faster if declared with the `register` storage class?

Like:

```
register int_fastY_t i;

```

\*(*Implying the premises above.*)

Or do they interfere with each other and decrease the performance?