Oscar Byström Ericsson
Oscar Byström Ericsson
Sadly `extension NBKDoubleWidth {` does not count as a declaration: ```swift #if SBI && swift(>=5.8) @available(iOS 16.4, macCatalyst 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4, *) extension NBKDoubleWidth { #else...
I'd also like to avoid making it integer specific, because that would make the un/signed integer protocols confusing (as they are binary).
Hm. Most of the Signed\ things I want to generalize are integer things, so I guess it would have to be integer related. Maybe I could call it something like...
There are some annoying things that come with trying to insert non-leaf protocols. Like, you get ambiguities if you try to customize existing BinaryInteger methods. It can be solved with...
I believe this would not be an issue if it were possible to constrain the default digit methods to a scope `where Self != Self.Digit`.
Hm. I'm not convinced it's a solution to the problem mentioned, but there are still other uses for it. More so with UIntXL (#33), where it is important to avoid...
The asymmetry of (#34) is an argument in favor of adding a duplicate requirement to NBKSignedInteger. Hm.
I suppose it's unclear what size this would give a manually resizable integer. Hm.
An alternative is committing to fixed-width by moving `init(bit:)` to NBKFixedWidthInteger. The rationale being that heap allocating a single bit is almost never what you intend to do.
One with...(\_:) instead of multiple free-function shims is Greatness™ > I have a dream ...of views without closures.