-
Notifications
You must be signed in to change notification settings - Fork 15
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
Open to replacing failure
with thiserror
?
#27
Comments
Absolutely! |
@jonhoo also, I was looking over the other issues and saw this:
My company is building out at least one large-ish rust system that uses faktory for job dispatch (and we already use faktory heavily in other languages), so I will likely be trying to upstream multiple PRs as part of that over the coming weeks/months/longer (depending on what issues we run into). I'm open to stepping up to the plate here- happy to talk more about what that'd look like and how I can help! |
@kitified That'd be amazing! I've added you as a maintainer of the GitHub project. I'll hold off on the crates.io release privileges for the time being, but as you ramp up on the project I'm happy to share that too :) Even though you have permissions now, please do keep submitting PRs and I'll do my best to give reviews in a timely fashion! |
Sounds great, will do! |
Hey there! I'm starting a new project using this library.
Now that
failure
is deprecated, and the ecosystem is moving towards a system where libraries report implementations ofError
, would you be open to a PR replacing usage offailure
with properError
implementations?The text was updated successfully, but these errors were encountered: