The current documentation often lacks necessary detail for functions. While the synopsis and a generic description of the main classes (decimal32_t, decimal64_t, decimal128_t) are present, there's lack of information, like preconditions or edge-case behaviors, for many functions.
Andrzej opened an issue tracking this towards the beginning of the review period. It'll be fixed.
Some examples aren't embedded directly in the documentation, but are merely mentioned as external files. While this prevents large blocks of code from cluttering the documentation, it imposes a burden on the user, who must manually navigate the repository to find these files. A much better solution would be to provide direct inks to these files. In this way, users could quickly jump to the code and return to the documentation, without the need to open a new browser window and manually look for the specific files.
Fair enough, and relatively easy to change.
I think the use of explicit constructors should be more clearly defined.
Yes, and the integer ones will be all marked explicit. Do you care to explicitly specify if you want the library accepted or rejected? You do not have to if you do not want to. Either way thank you for the comments. Matt