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

Upgrade thiserror to 2.0 and disable default features #506

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

brownjohnf
Copy link

Disable default-features on thiserror

We're barely using thiserror at all in moka, and we don't require any of
thiserror's features.

We might also want to consider not using thiserror at all and pruning
that whole dependency tree.

Upgrade thiserror to 2.0

Thiserror has had a 2.0 release that does include breaking changes but
does not appear to impact moka's use of thiserror.

By upgrading, we can stay closer to the latest version of thiserror and
avoid needing to compile multiple versions of thiserror in consumers who
are themselves using a newer version of thiserror.

Thiserror has had a 2.0 release that does include breaking changes but
does not appear to impact moka's use of thiserror.

By upgrading, we can stay closer to the latest version of thiserror and
avoid needing to compile multiple versions of thiserror in consumers who
are themselves using a newer version of thiserror.
We're barely using thiserror at all in moka, and we don't require any of
thiserror's features.

We might also want to consider not using thiserror at all and pruning
that whole dependency tree.
@brownjohnf
Copy link
Author

New contributor here! I was just working on optimizing a dependency tree in a project, and noticed that we were pulling in 2 versions of thiserror, the older one coming from moka.

As I mentioned in one of the commits, I also noticed that we're barely using thiserror here; if you were interested I'd be happy to PR a change to just drop it as a dependency and manually impl Error for the one place (that I've seen) we're using it outside of tests. Maybe we could just move it to a dev-dependency or something.

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.

1 participant