Skip to content

Don't shadow VersionTupleSyntax.components. #177

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 1 commit into from
Jan 10, 2024

Conversation

grynspan
Copy link
Contributor

@grynspan grynspan commented Jan 10, 2024

Since we first wrote the code in VersionTupleSyntaxAdditions.swift, a components property has been added to VersionTupleSyntax. We shouldn't shadow it with our own property (and we should call it in order to more efficiently and correctly get version info than we do now.)

Checklist:

  • Code and documentation should follow the style of the Style Guide.
  • If public symbols are renamed or modified, DocC references should be updated.

Since we first wrote the code in VersionTupleSyntaxAdditions.swift, a `components` property has been added to `VersionTupleSyntax`. We shouldn't shadow it with our own property (and we should call it in order to more efficiently and correctly get version info than we do now.)
@grynspan
Copy link
Contributor Author

@swift-ci please test

@stmontgomery stmontgomery added the enhancement New feature or request label Jan 10, 2024
@grynspan grynspan merged commit 7d4fe42 into main Jan 10, 2024
@grynspan grynspan deleted the jgrynspan/no-shadow-version-components branch January 10, 2024 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants