Skip to content

Swift: Add integral type classes #11841

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

Merged
merged 8 commits into from
Jan 13, 2023

Conversation

MathiasVP
Copy link
Contributor

I had these lying around as left-overs from some unrelated work, and they seem too useful to throw away (since most other languages have versions of these).

@MathiasVP MathiasVP requested a review from a team as a code owner January 9, 2023 09:44
@MathiasVP MathiasVP added the no-change-note-required This PR does not need a change note label Jan 9, 2023
@github-actions github-actions bot added the Swift label Jan 9, 2023
Copy link
Contributor

@geoffw0 geoffw0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for finding and sharing this work. I think it needs a bit more polish before we merge it though, e.g. there really ought to be minimal test coverage. I know you have other priorities - let me know if you'd prefer me to do the changes to this PR?


/**
* A numeric-like type. This includes the types `Character`, `Bool`, and all
* the integer-like types.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two things:

  • isn't a floating point type numeric as well?
  • other languages don't seem to include Bool as a numeric type.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. I agree with both of these observations 👍

Co-authored-by: Geoffrey White <[email protected]>
@MathiasVP
Copy link
Contributor Author

Thanks for finding and sharing this work. I think it needs a bit more polish before we merge it though, e.g. there really ought to be minimal test coverage. I know you have other priorities - let me know if you'd prefer me to do the changes to this PR?

Thanks! Yeah, I agree with all those comments. I'm not sure what the best testing approach to this would be. A naive thing would be a ql test that just selects all the relevant types from a large .swift file, but I fear that this will just be a .expected file that we just blindly accept test changes to.

I'd really appreciate if you could take over this PR 🙇.

@geoffw0
Copy link
Contributor

geoffw0 commented Jan 9, 2023

No problem, I'll finish this PR probably this week.

@geoffw0
Copy link
Contributor

geoffw0 commented Jan 12, 2023

I've made a PR onto this PR here: MathiasVP#5

@MathiasVP I suggest you review that and merge it (into this PR) when you're happy, then I'll merge this PR into main, hence everything will have had 2+ sets of eyes on it.

Any other reviewers, you're welcome to comment on there or here as well.

Swift: Work on integral type classes
Copy link
Contributor

@geoffw0 geoffw0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

I will do a follow-up to use the new classes in queries.

@geoffw0
Copy link
Contributor

geoffw0 commented Jan 13, 2023

Checks failed - "Unable to connect to azure.archive.ubuntu.com" - sounds like we should retry in a few hours?

@MathiasVP
Copy link
Contributor Author

Checks failed - "Unable to connect to azure.archive.ubuntu.com" - sounds like we should retry in a few hours?

Yeah. I already retried some other failing CI checks, and they seemed to succeed now. I'll just try restarting the final one right away.

@MathiasVP
Copy link
Contributor Author

Bahh... Failed again 😭.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-change-note-required This PR does not need a change note Swift
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants