Swift updates #373
Closed
Swift updates #373
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ator into radianttap-swift-templates
* Don’t import C style headers in Swift code * Add a space between “public” and “private(set)” to avoid “publicprivate” in code. * Don’t declare “open” items in public extension * Use “entityName” instead of “entityName()”
|
I believe that failing tests are probably due to Travis not having an Xcode 10 option right now. The test failures complain that Using |
Closed
|
Closing this out for now because it's not quite ready and I don't want to have Travis keep sending messages about failing tests while I finish with it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of Changes
Updates for better Swift-iness, mostly based on changes in #368 (thanks a ton, @radianttap). Some additional changes have been incorporated:
Please nobody merge this until Xcode 10 is released because as the branch name implies, these changes require Swift 4.2.