Skip to content

Typos: test/* (misc folders in test) #75033

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

Closed
wants to merge 1 commit into from
Closed

Typos: test/* (misc folders in test) #75033

wants to merge 1 commit into from

Conversation

Sajjon
Copy link
Contributor

@Sajjon Sajjon commented Jul 7, 2024

Fix typos in test/* ((misc folders in test)

This is one batch of many PRs fixing typos, see the tracking issue.

Copy link
Contributor

@bnbarham bnbarham left a comment

Choose a reason for hiding this comment

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

Thanks @Sajjon! Just the two length issues as in the other PRs, LGTM otherwise.

@AnthonyLatsis
Copy link
Collaborator

@swift-ci please smoke test

@Sajjon
Copy link
Contributor Author

Sajjon commented Aug 8, 2024

@bnbarham @AnthonyLatsis Sorry for downtime, I was on vacation, but back now.

I've squashed and applied changes on top of main ( commit: 906efcb )

Anything I need to do to get this merged?

@ahoppen
Copy link
Member

ahoppen commented Aug 8, 2024

@swift-ci Please smoke test

@Sajjon
Copy link
Contributor Author

Sajjon commented Aug 9, 2024

@AnthonyLatsis thanks for the help! I've reverted/fixed your suggestions by amending the commit;

Screenshot 2024-08-09 at 07 42 40 Screenshot 2024-08-09 at 07 53 20

Let me know if there is anything else needed to be done!

@AnthonyLatsis
Copy link
Collaborator

@swift-ci Please smoke test

@vivoxfold3
Copy link

⚠️⚠️⚠️Caution⚠️⚠️⚠️

This user is attempting to execute the first step of a supply chain attack, attempting to break free from the 'first-time contributor' status. The user opened a similar PR in all other repositories on the same day. He also stole pictures of other users to make them look like real people.

There are still hundreds of submissions like this, and they can be fixed at once. They will be submitted in multiple batches, and this is one part of them

@Sajjon

This comment has been minimized.

@@ -173,7 +173,7 @@ func rdar21080030() {
if s.count() == 0 {} // expected-error {{cannot call value of non-function type 'Int'}}
}

// <rdar://problem/21248136> QoI: problem with return type inference mis-diagnosed as invalid arguments
// <rdar://problem/21248136> QoI: problem with return type inference misdiagnosed as invalid arguments
Copy link
Contributor

Choose a reason for hiding this comment

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

Please leave the spelling here alone, as you can't rename the record it refers to.

@@ -2,7 +2,7 @@
if 'asserts' not in config.available_features:
config.unsupported = True

config.subsitutions = list(config.substitutions)
config.substitutions = list(config.substitutions)
Copy link
Contributor

Choose a reason for hiding this comment

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

This might cause a change in behavior. Are we certain it's correct?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Looks very much like a typo in a line that did not prove necessary.

@compnerd Do we need this line removed or corrected?

@@ -93,10 +93,10 @@ struct UnavailableType {
var storedClosure: Int = { .random() ? 0 : 1 }()

@Wrapper
var wrappered = .random() ? 0 : 1
var wrapped = .random() ? 0 : 1
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm probably being too paranoid, but the identifier wrapped is, in some really specific cases, special for property wrappers. I don't think it means anything special here, but out of an abundance of caution I'd be more comfortable giving this a name that completely avoids that problem, like wrappedProperty.

@Sajjon Sajjon closed this by deleting the head repository Mar 17, 2025
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.

6 participants