<div dir="ltr"><div>Unless I am missing something the endianness is a runtime property.</div><div>You should provide API that allow to serialize based on compile-time provided endianess (either two functions different names, or templated by endianess), as I do not want to pay the prize of runtime dispatch overhead (+unnecessary code bloat) in scenarios where endianess is known up-front.</div><div><br></div><div>Regards,</div><div>Maciej<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">czw., 5 mar 2020 o 20:38 Lyberta via Std-Proposals &lt;<a href="mailto:std-proposals@lists.isocpp.org">std-proposals@lists.isocpp.org</a>&gt; napisał(a):<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">This paper proposes fundamental IO concepts, customization points for serialization and deserialization and streams for memory<br>
and file IO.<br>
<br>
It was initially based on design similar to iostreams but most of it was changed to be in line with modern C++20 practice. In<br>
particular, the proposal embraces type erasure instead of virtual functions, exceptions instead of operator bool() and<br>
customization points instead of arithmetic shift operators.<br>
<br>
During benchmarking of sequential file IO on Linux proposed std::io::input_file_stream is ~30% faster than std::FILE and ~45%<br>
faster than std::ifstream while proposed std::io::output_file_stream is ~38% faster than std::FILE and ~60% faster than<br>
std::ofstream.<br>
<br>
I&#39;m looking for a champion to present the proposal in Varna.<br>
-- <br>
Std-Proposals mailing list<br>
<a href="mailto:Std-Proposals@lists.isocpp.org" target="_blank">Std-Proposals@lists.isocpp.org</a><br>
<a href="https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals" rel="noreferrer" target="_blank">https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals</a><br>
</blockquote></div>

