Eldred Habert

> The issue is when that extra tooling stops being extra tooling and becomes part of the language — then the tool is no longer a bonus feature and it...

I have been repeatedly helped by `-Wtruncation` catching some fixed-point manipulation mistakes in this past week, so I have zero idea what ”so much trouble” may be referring to.

I'm aware of your style, but that makes one example on each side of the balance, so AFAICT no definite sway. I lack more data points to make an informed...

> As I said, the happy medium that makes both sides of the debate happy is to separate the checks into other tools, so people can integrate the tools/checks they...

> But I do specifically set `=1` not `=2`, because I expect to be able to bit-negate any valid N-bit value and have it stay within N bits. Even if...

Thank you for pointing that out! I think Pino's suggestion is very good too. Is the bit order not explained by the text? Is the description unclear? If either of...

Another pro of MarkDown: [mandown](https://gitlab.com/kornelski/mandown), which *might* be usable to back-shim the documentation for people who cling to the terminal regardless. (Probably used as To explore also: - [ ]...

Then if that's the axis we're prioritising, MarkDown is *by far* the way to go. It massively helps with keeping rendering consistent, is *far* les verbose and “ceremonious” than HTML...

> Good point! I'd forgotten about HTML-in-Markdown for edge cases. I insist on the “if absolutely necessary” part, because HTML tags exclude exporting to other formats (PDF and/or `man` page,...

This seems to be decided, but I'd like this to *not* happen in 0.9.0, since it's going to require a *lot* of effort, including coordinated across two repos and a...