Skip to content

[stdlib] StaticString: extension per conformance #30702

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
Apr 20, 2020

Conversation

benrimmington
Copy link
Contributor

This is a stylistic change, to prepare for additional protocol conformances.

(e.g. Make StaticString conform to Hashable)

@benrimmington
Copy link
Contributor Author

@milseman Please could you take a look, or suggest someone else to review this?

Do you know if this kind of change to protocol conformances is allowed?

@CodaFi
Copy link
Contributor

CodaFi commented Apr 14, 2020

I hope this is harmless

@swift-ci test

@CodaFi
Copy link
Contributor

CodaFi commented Apr 14, 2020

@swift-ci test source compatibility

@CodaFi
Copy link
Contributor

CodaFi commented Apr 15, 2020

Debug failure is probably related to a recent type reconstruction patch.

@benrimmington
Copy link
Contributor Author

@slavapestov Please could you comment on whether this change is resilient?

I couldn't find mention of it in either your blog post or the documentation.

@CodaFi
Copy link
Contributor

CodaFi commented Apr 19, 2020

@swift-ci test source compatibility Debug

@CodaFi
Copy link
Contributor

CodaFi commented Apr 19, 2020

The change is resilient. My comment was more about hoping the type checker wasn't relying on a specific ordering of declarations here.

@CodaFi
Copy link
Contributor

CodaFi commented Apr 20, 2020

⛵️

@CodaFi CodaFi merged commit 177bd24 into swiftlang:master Apr 20, 2020
@benrimmington benrimmington deleted the static-string-extensions branch April 20, 2020 17:00
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.

2 participants