John McFarlane

> My unfiltered gut-reaction is to leave the preliminary work of uintwide_t closely as-it-is. A lot of people are using it. Big name changes and redesings of this scale might...

Sounds good. And yes, it won't be trivial, but I think the results will be something many users will be eager to adopt. For reference, CNL v2 (which is yet...

> Let's work together --- in the sense that we have already been doing, or if you like, share the coding even more (all at your option, of course)? There...

tl;dr probably yes, it requires random access if you're using `operator[]` but that's no big deal. It's a good question. You're really the one to answer that because it essentially...

Great! However, this can be pursued in isolation from the kinds of refactors covered by this thread. At the end of, you may find you can make numbers out of...

YW. Don't be afraid to add an accessor akin to `vector::data()`: ```c++ constexpr Container& data() noexcept; constexpr Container const& data() const noexcept; ```

Happy New Year! Update: I pretty-much integrated wide-integer into CNL by copy-pasting _uintwide_t.h_ into the CNL repo. Then I've mulled over it. I'm still not comfortable with introducing `::math` to...

I'm happy to continue working on the namespace change. I need to test that it works with CNL anyways. On Wed 5 Jan 2022, 18:38 Christopher Kormanyos, ***@***.***> wrote: >...

Cool. I've thrown together a PR in #163. LMK what you think.

Hi Chris, I've been following progress of your library from a distance and occasionally updating my version of the main header. The external memory silicon-chips sounds fascinating but I'm not...