Address the exceptionally high build time. #495
Merged
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.
Swift 3 compiler is less performant in situations that need sophisticated inference. It appears not to be an issue for Swift 4 though. πββοΈ
While the constraints have been tightened, IMO it shouldn't be considered API breaking, since the
Property
requirements mandateNoError
, and theError
associated type is just an implementation detail that is alwaysNoError
at conformance time.Ideally we would get rid of these in RAS 3.0 by constraining
PropertyProtocol
withError == NoError
.Checklist