Adding nfloat throughout to prevent possible data loss. #11
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
slodge
added a commit
that referenced
this pull request
Dec 9, 2014
Adding nfloat throughout to prevent possible data loss.
Collaborator
|
Thanks - looks good :) (Just hope my eyes still work well enough to notice when Apple get to unfathomable retina+++ :)) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
NSLayoutConstraint now takes an nfloat. I modified the FluentLayout API to also take nfloats (optionally). No code changes should be necessary by implementers and no one should worry about data loss, when eventualy Apple's products have unfathomable resolutions.