# Unstable hash architecture

**URL:** <https://internals.rust-lang.org/t/unstable-hash-architecture/578>\
**Category:** ideas (deprecated)\
**Created:** [September 30, 2014, 2:26pm UTC](https://internals.rust-lang.org/t/unstable-hash-architecture/578 "2014-09-30T14:26:27Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![arthurprs](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/arthurprs/32/233_2.png) [@arthurprs](https://internals.rust-lang.org/u/arthurprs)\
**Post date:** [October 4, 2014, 3:22am UTC](https://internals.rust-lang.org/t/unstable-hash-architecture/578/12 "2014-10-04T03:22:15Z")

</div>

> [@Jurily](#):
>
> All integers including u8 observe endianness, so they must be hashed individually.

Why rust requires the hash code to be portable across little and big endian? If you put that aside all primitive slices (thus Vec, str and String) can be hashed in one call. In fact anything else will impose a huge slowdown (as you already stated).

---

_[View the full topic](https://internals.rust-lang.org/t/unstable-hash-architecture/578)._