This repository has been archived by the owner on Aug 13, 2021. It is now read-only.
Resolve Xcode 9 build failures #123
Merged
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
romoore
suggested changes
Oct 31, 2017
| @@ -0,0 +1,30 @@ | |||
| /* | |||
| Copyright 2016-present The Material Motion Authors. All Rights Reserved. | |||
|
Done. |
|
Is this updated in the pod file? I get these errors if I instlal with the pod still |
huangboju
pushed a commit
to huangboju/material-motion-swift
that referenced
this pull request
Feb 3, 2020
* Xcode 9 build failure fixes. * Add comment. * Update copyright year.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Type aliases in Swift only allow us to indicate that
Tconforms to a single type, so in order to specify that our springTconforms toZeroableandSubtractablewe introduced a composite type,ZeroableAndSubtractable. Prior to Swift 3.2 conforming toZeroableandSubtractableappeared sufficient to meet the check for conforming toZeroableAndSubtractable. With Swift 3.2 it appears this is no longer sufficient, so we need to declare explicit conformity toZeroableAndSubtractablewhere applicable.