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.

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

[Swift 6.0]: Update armstrong number with new testing files #784

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

meatball133
Copy link
Member

@meatball133 meatball133 commented Dec 17, 2024

Swift 6.0 introduces the int128 type, allowing for a larger number of tests to be added without external libraries. Seemingly swift doesn't have accurate exponational functions for int128 so we will have to wait a bit further.

@meatball133 meatball133 added this to the Swift 6.0 milestone Dec 17, 2024
Copy link
Contributor

Hello 👋 Thanks for your PR.

This repo does not currently have dedicated maintainers. Our cross-track maintainers team will attempt to review and merge your PR, but it will likely take longer for your PR to be reviewed.

If you enjoy contributing to Exercism and have a track-record of doing so successfully, you might like to become an Exercism maintainer for this track.

Please feel free to ask any questions, or chat to us about anything to do with this PR or the reviewing process on the Exercism forum.

(cc @exercism/cross-track-maintainers)

@meatball133 meatball133 mentioned this pull request Dec 17, 2024
4 tasks
@meatball133 meatball133 changed the title [Swift 6.0]: Update armstrong number with int128 and new testing files [Swift 6.0]: Update armstrong number with ~~int128 and~~ new testing files Dec 17, 2024
@meatball133 meatball133 changed the title [Swift 6.0]: Update armstrong number with ~~int128 and~~ new testing files [Swift 6.0]: Update armstrong number with new testing files Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant