John McFarlane

Suggestion: * Start by breaking up the target, _test_uintwide_t_, in test/unit/_impl/wide-integer.cpp each one target per source file. * Invoke the tests with `ctest --output-on-failure --parallel 8` to run 8 at...

I'm curious to know three things: 1. What is the need of these very specific sub-limb widths, 16, 24 and 32? This whole constraint seems very puzzling and I wonder...

Great answers, thanks! I'll concentrate on 3... > And I do not really want to tackle that at the moment, as my brain needs to figure out an easy way...

I tried adding that 'simple' constructor for 128-bit integers. And of course it's far more complex a change that I anticipated. Much supporting code in the file would need to...

That's a fairly good list. There may be more but those are major needs. However, what support is provided is a choice made *after* the decision to support `__int128` at...

OK, then I need to make the changes to CNL. They will mostly be removal of code to support `__int128` so it will be a pleasure! Note, however, that in...

@ckormanyos no problem. I can work with the multiple directories, headers, namespaces with straight-forward workarounds for now, so no hurry. If CNL comes to depend on wide-integer, they will end...

Unfortunately, `math` is not a good choice for the reason you mention and the ones I gave above: just because it's maths-related doesn't lead to wanting it in a "math"...

That sounds like a good plan. TBH I haven't looked at the integration since I started to write my error handling document. I hope to turn back to it soon.

OK, I'm up to speed with the changes. We can probably resume this conversation. Much has been addressed since the original post. Would you like me to start a new...