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

Using host byte order for PortNumber to fix Ord instance. #347

Merged
merged 1 commit into from Aug 30, 2018

Conversation

kazu-yamamoto
Copy link
Collaborator

This should fix #346.

Copy link
Collaborator

@Mistuke Mistuke left a comment

Choose a reason for hiding this comment

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

Thanks @kazu-yamamoto! Looks good to me. The appveyor failure seems to be a connection issue.

kazu-yamamoto added a commit to kazu-yamamoto/network that referenced this pull request Aug 30, 2018
@kazu-yamamoto kazu-yamamoto merged commit f423712 into haskell:master Aug 30, 2018
@kazu-yamamoto kazu-yamamoto deleted the portnumber branch August 30, 2018 01:24
kazu-yamamoto added a commit to kazu-yamamoto/network that referenced this pull request Aug 30, 2018
@kazu-yamamoto
Copy link
Collaborator Author

@Mistuke Thank you for your review.
Merged and applied the same patch also to 2.7.

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.

Ord for PortNnumber behaves strangely
2 participants