-
Notifications
You must be signed in to change notification settings - Fork 440
Make String
conform to ExpressibleAs
protocols
#335
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
Make String
conform to ExpressibleAs
protocols
#335
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. This is great. From a quick glance it looks to me like there are a few unrelated changes in here that were caused by a new protocolMap.py
in the main swift repo.
@swift-ci Please test |
String
conform to ExpressibleAs
protocolsString
conform to ExpressibleBy
protocols
Will update code and rebase when #337 is merged |
7fd2710
to
889c765
Compare
I have rebased this and swiftlang/swift#40128 |
@kimdv If you want, I would encourage you to request commit access to Swift (https://www.swift.org/contributing/#commit-access). I think you have accumulated more than the encouraged 5 non-trivial pull request by now. 😉 With commit access you’ll be able to trigger CI yourself. |
@swift-ci Please test |
Build failed |
Build failed |
Will rebase when #334 is merged. |
9a134cc
to
cfb7d95
Compare
cfb7d95
to
674431e
Compare
String
conform to ExpressibleBy
protocolsString
conform to ExpressibleAs
protocols
@swift-ci Please test |
Build failed |
Build failed |
This is some ideas I got, while I was playing around with #331 .
Not sure if it's correct to make some if this assumptions I make in the StringConvenienceInitializers.swift?
I think we can make those assumptions because it is simple types.
But let me hear if there is anything!
The test cases are getting more and more clean and easy to read 🎉