Doc. no.: | D0803R1 |
Date: | 2017-11-10 |
Reply to: | Beman Dawes <bdawes at acm dot org> |
Audience: | Library Evolution |
The Boost Endian library manipulates the endianness of integers and user-defined types. It provides three approaches to dealing with endianness: conversion functions, buffer classes, and arithmetic classes. Each approach has use cases where it is preferred by users over the other approaches, but adding all three approaches to the standard library would likely be too much of a good thing. The purpose of this RFC is to determine interest in adding the Boost conversion functions alone to the C++ standard library or a library TS.
The Boost Endian documentation (www.boost.org/libs/endian/doc) provides an overview and detailed technical specifications for the conversion functions, arithmetic types, and buffer types.
A separate discussion covers choosing between the three approaches provided by the library.
For those not interested in plowing through the entire documentation, the Overall FAQ, Conversion FAQ, Arithmetic FAQ, and Buffers FAQ answer a lot of question likely to arise during standardization.
Endianness conversion functions would be pure additions to the
standard library and would break no existing user code (modulo the usual
namespace std
caveats).
The Boost Endian reference documentation for Conversion follows the standard library's Method of description [description], so provides a fairly close approximation of what proposed wording would look like. Actual proposed wording will be provided in a proposal document if the library is of interest to the committee. Names will need the usual review.
R1: Limits proposal to the conversion functions. KISS.
R0: Considers adding all three endianness approaches to the standard library.
It is premature to discuss whether to target a TS or the IS. We need to have an acceptable proposal in hand and see where we are in the release cycle before deciding on the target.
The original design for the arithmetic classes was developed by Darin Adler based on work by Mark Borgerding. The Boost documentation acknowledges 45+ other people.