Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove: TripleInt #124

Open
oscbyspro opened this issue Nov 3, 2024 · 1 comment
Open

Remove: TripleInt #124

oscbyspro opened this issue Nov 3, 2024 · 1 comment
Labels
subtraction huh? where did it go?
Milestone
Ultimathnum 0.12.0

Comments

@oscbyspro
Copy link
Owner

oscbyspro commented Nov 3, 2024 •
edited
Loading

The TripleInt model is cute, but it is not a BinaryInteger so it adds complexity. (#108) can't abstract it, so even the simplest forwarding rules require bespoke testing strategies. I'm sure there's a better way of hosting its algorithms. Like, TripleInt.division3212(normalized:) is the only non-trivial algorithm.
@oscbyspro oscbyspro added the subtraction huh? where did it go? label Nov 3, 2024
@oscbyspro oscbyspro added this to the Ultimathnum 0.12.0 milestone Nov 3, 2024
@oscbyspro
Copy link
Owner Author

oscbyspro commented Nov 3, 2024 •
edited
Loading

I suspect an eventual VectorInt will supersede all things DoubleInt, but still.

oscbyspro added a commit that referenced this issue Nov 4, 2024
@oscbyspro
Skip rework of TripleInt tests (#124).
46af546
oscbyspro added a commit that referenced this issue Nov 9, 2024
@oscbyspro
Suppress silly swift-testing warnings (#110)(#124).
f986cd6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
subtraction huh? where did it go?
Projects
None yet
Milestone
Ultimathnum 0.12.0
Development

No branches or pull requests
1 participant
@oscbyspro