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.

Sign up for GitHub

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

Jump to bottom

Use a more standard Result type instead of our own #11

Closed
iphydf opened this issue Jan 5, 2017 · 2 comments
Closed

Use a more standard Result type instead of our own #11

iphydf opened this issue Jan 5, 2017 · 2 comments

Comments

@iphydf
Copy link
Member

iphydf commented Jan 5, 2017

We're using Data.MessagePack.Result, which has nothing to do with msgpack. We should use a standard one from some package.
@l29ah
Copy link
Contributor

l29ah commented Jun 24, 2020 •
edited
Loading

Yeah, it's Either String a.

@iphydf
Copy link
Member Author

iphydf commented Feb 12, 2022

This is done now. We're using Either DecodeError a now.

@iphydf iphydf closed this as completed Feb 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@l29ah @iphydf