You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMO, bytes are more honest and correct than octets (for bool and some enums, at least). For primitives such as char and u8, and exact bit-count is better than bytes
The text was updated successfully, but these errors were encountered:
Rudxain
changed the title
Disambiguate "byte" size for all docs
Disambiguate "byte" size
Nov 13, 2024
I don't think we support any target where a byte is anything other than 8 bits, just like we don't support any systems that use something other than two's complement for signed integers.
The Glossary and "Type Layout" don't specify the size of a "byte".
I think it's worth being explicit about that.
BTW, the
bool
reference seems somewhat contradictory:size_of::<bool>() == 1
implies platform-dependent byteu8
(guaranteed octet)Note
Previous discussions:
IMO, bytes are more honest and correct than octets (for
bool
and someenum
s, at least). For primitives such aschar
andu8
, and exact bit-count is better than bytesThe text was updated successfully, but these errors were encountered: