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

feat: display formatted errors. #56

Merged
merged 3 commits into from
Mar 27, 2016
Merged

feat: display formatted errors. #56

merged 3 commits into from
Mar 27, 2016

Conversation

cristianoliveira
Copy link
Contributor

Hi there.

I've implemented the trait Display for the enum errors. That way we can display formatted messages for users when necessary instead of the debug version.

Feel free to review.

Cheers!

format!("{}",
Error::Io(io::Error::new(io::ErrorKind::Other, expected))
)
);
Copy link
Member

Choose a reason for hiding this comment

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

There's some kind of indentation mistake here. Also, the rest of the code is indented 2 chars, not 4.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ooops I am used to ident that way by the (still under development) style guide. Let me fix it. :)

Copy link
Member

Choose a reason for hiding this comment

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

Yeah I want to change rsnotify to the rust style some day, but for now 'll just keep it consistent.

@passcod
Copy link
Member

passcod commented Mar 27, 2016

Looks good, thank you :)

@cristianoliveira
Copy link
Contributor Author

Thank you for this lib. I am using it in one of my projects and it is helping a lot!

@passcod
Copy link
Member

passcod commented Mar 27, 2016

Glad you like it!

@passcod passcod merged commit 8f66976 into notify-rs:master Mar 27, 2016
@passcod
Copy link
Member

passcod commented Mar 27, 2016

Released in 2.5.5

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.

None yet

2 participants