Splitting implementation into several files in anticipation of growth of the code base. #12
Conversation
This file contains hidden or 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
… of the code base.
|
Foundation's tests build & pass on OS X and Linux with this change. |
mike-ferris
pushed a commit
that referenced
this pull request
Dec 7, 2015
Splitting implementation into several files in anticipation of growth of the code base.
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.
My general goal here is to go by the general pattern of defining things in their own files. I have split the assertion functions into XCTAssert.swift, I have also created separate a file for XCTestCaseProvider and another for the XCTestCase protocol and its extension. Finally XCTest.swift remains with the XCTMain function and some attendant global state and the structs used to track it.