Tiny Pitch: `ByteOrder` type

[YOCKOW]

@maartene

Do you also propose to create bridges to/from __CFByteOrder?

Honestly I'm reluctant to do it because CoreFoundation via Swift is not flawlessly cross-platform.

---

@benrimmington

I think CFByteOrderGetCurrent() and NSHostByteOrder() are only available on Apple platforms.

At least CFByteOrderGetCurrent() is also available on Linux: Code
At any rate, CF-APIs seem not to be available on Windows.
A bona-fide cross-platform type/API is desirable.

---

@Nickolas_Pohilets

I would prefer to have a type that models known byte order, and combine it with Optional<> when byte order can be unknown.

Definitely.
I was too affected by CoreFoundation’s C-style API.

---

@ktoso

Wouldn't it be better to hold off introducing such types for when we tackle the long standing issue of introducing a "good" ByteBuffer type?

@Karl

Other than querying the machine's native endianness, I'm not sure what additional value a ByteOrder type would offer over the existing APIs.

Sorry, but I didn’t write enough background of this pitch.
This pitch has an aspect of response to the other pitch “Unicode Processing APIs” which include introducing such type.
I thought it is necessary to discuss about the type itself separately.