Skip to content

Conversation

@bharat
Copy link

@bharat bharat commented Mar 30, 2017

This is on top of #421

Bharat Mediratta added 6 commits March 29, 2017 17:57
1. Change all explicit calls to .debugDescription over to
   String(describing:). This preserves existing behavior which was
   happening implicitly before swift 3.1

2. Use CGFloat.pi instead of CGFloat(Double.pi), and fix an issue where
   I accidentally negated one of the values in an earlier commit
Separate them out from the non-API related warning fixes.
@bharat bharat changed the title Resolve LoopKit deprecation warnings by using new APIs Swift 3.1 - Update APIs to resolve LoopKit 1.2.0 deprecation warnings Mar 30, 2017
@bharat bharat changed the title Swift 3.1 - Update APIs to resolve LoopKit 1.2.0 deprecation warnings Swift 3.1 - update APIs to resolve LoopKit 1.2.0 deprecation warnings Mar 30, 2017
Bharat Mediratta and others added 2 commits March 30, 2017 20:04
We were accidentally getting 1.2.1 because carthage considers it to be
compatible when you use the ~> notation.
@bharat bharat closed this Mar 31, 2017
@bharat bharat deleted the dev-3.1-loopkit-api-warning-fixes branch April 1, 2017 17:02
ps2 pushed a commit that referenced this pull request Jul 17, 2021
ps2 pushed a commit that referenced this pull request Jul 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant