Excluded it when exceptions are off.

Link to P0037 broken and title sucks

Currently disabled via common.cmake.

As with the fp library, make multiprecision.h simpler by using the boost::multiprecision::cpp_int (or whatever) types.

In particular:

• compound assignment
• bitwise operations
• shift operators - static and dynamic
• basically anything in this list that can be overloaded

Mention predictability.

and replace hacky instruction about -fno-omit-frame-pointer in index.md

With elastic type.

As mentioned in section Alternative Return Type Policies of P0037R1.

Multiplication between 64-bit numbers should overflow and/or cause compiler errors on platforms with no 128-bit integers and MSVC++ doesn't have 128-bit integers. But tests pass. Make sure tests are robust enough.

Follow up on the helpful advice provided by Ryhor.

And repr_type to rep in line with chrono.

Section of P0037

Suggestion via Paul Robinson:

"Exponent" will typically be negative
The proposal doesn't discuss this but the typical use-case of a value
with both integer and fractional digits would require Exponent to be
negative. For example make_ufixed<4, 4> would have to be the same type
as fixed_point<uint8_t, -4> (in order for the stated maximum/minimum
values to work out correctly). This is perfectly fine, but when it
comes to working out the wording in the standard, this would definitely
be worthy of an example or footnote.

Move installation instructions to README.md
Clearer link
link in other direction
Better blurb/highlights in index.md and README.md
Include notes about cmark, Doxygen and boost
Links to source in index.mf

On main instruction page, perf stat ./run_benchmarks should read perf record -g ./run_benchmarks.

Such that built-in integer resize can be defined as:

template <typename UnsignedInteger>
struct resize 
    : resize_family
    <
        UnsignedInteger, uint8_t, uint16_t, uint32_t, uint64_t, unsigned __128int_t
    > {};

template <typename SignedInteger>
struct resize 
    : resize_family
    <
        SignedInteger, int8_t, int16_t, int32_t, int64_t, signed __128int_t
    > {};

There is no licensing information provided, could this please be clarified? Thank you.

Generally, common_type involving fixed_point should behave closer to ReprType.

Alternative Return Type Policies suggests work that has since been executed upon.

include all_of_this

To answer the Jacksonville questions:

• How does resize work with user-supplied representations? and
• The specialization of numeric limits is good. We wonder how it might apply to unbounded types.

Use the phrase fixed-point more often in line with floating-point and integer/integral.

This style

template <typename N>
struct S;

is not as colorful as

template <typename N>
struct S;

Claims no loss of bits. And hey, why not actually implement those!

Possibly as named function?

cpp_int proves that sizeof and resize are not complements of one another. What about set_width? It takes bits, not bytes. Parameter can be unsigned - for now at least.

move multiply etc. into sg14 and remove promot and trunc etc.

Casting where all three of signage, integer digits and fractional digits of the destination match or exceed the source should not be explicit.

Remove code surrounded in _GLIBCXX_USE_INT128 from type_traits.h. It can all live in bits/int128.h.

Also floating-point literals for elastic equivalent.

"straddle two 'homes"

Convert these functions to C++11 constexpr type and add to fixed_point_utils.h.

but maybe to sub-folder auxiliary and move elastic there too

E.g. an instruction that multiplies with saturation, then shifts right by 15 digits.

don't throw spare bits at fractional_digits!

As suggested by Paul Robinson

"Named arithmetic functions" (promote_*)

via an alias

Very touchy subject, so move e.g. std::make_unsigned<fixed_point<>> to sg14 namespace.