Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for decoding UInt and UInt64 #396

Merged
merged 1 commit into from
Jul 29, 2016

Conversation

gcox
Copy link
Contributor

@gcox gcox commented Jul 23, 2016

Tried to update the TestModelNumerics struct cleanly but ran into the "Expression was too complex to be solved in reasonable time" bug in Swift after I added the 3 required properties to the existing struct. That's why I added the TestModelUnsignedNumerics struct.

@@ -36,6 +36,9 @@ struct TestModelNumerics {
let double: Double
let float: Float
let intOpt: Int?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trailing Whitespace Violation: Lines should not have trailing whitespace. (trailing_whitespace)

@gcox gcox changed the title Support for encoding UInt and UInt64 Support for decoding UInt and UInt64 Jul 23, 2016
@gcox gcox force-pushed the unsigned-integer-support branch from 0dc5879 to 0fea858 Compare July 23, 2016 15:04
@gcox
Copy link
Contributor Author

gcox commented Jul 24, 2016

I'm happy to redo this change on the Swift-2.3 branch if it should go there first

@jshier
Copy link
Contributor

jshier commented Jul 24, 2016

You can get around the "too complex" errors by breaking the curry call into its own let. If that's not enough, you can also type the return method, as explained here.

@gfontenot
Copy link
Collaborator

Neat, thanks! I think we could merge this into master and then I'll cherry-pick it into a new release for 2.3 since there's no reason not to backport it.

@gfontenot gfontenot merged commit 0fea858 into thoughtbot:master Jul 29, 2016
@gfontenot
Copy link
Collaborator

I worked around the too complex issues and merged this into master. I'm also cutting 3.1 with this change in it.

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.

4 participants