connor horman via Std-Proposals:
> I am working on a library in C++ that has IO Capabilities, and as part of
> the library, I define a couple of named requirements that types being
> written or read “raw”

Obvious note that this makes data non-portable and only useful for
inter-process communication on the same ABI.

I'm working on a proposal that provides safe and portable IO by default:

https://github.com/Lyberta/cpp-io

Unsafe IO such as memcpy-ing structs can be coded as specializations in
my design.