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

Avoid returning errors where possible #82

Open

e00E opened this issue May 17, 2021 · 1 comment

Contributor

e00E commented May 17, 2021

Next breaking release that we make, I think we can remove the fallibility from
the Arbitrary trait and all the Unstructured methods.

This wasn't addressed in the discussion about 1.0 #62 .

Is this still something we want to do? Are you open for a PR implementing it?

The text was updated successfully, but these errors were encountered:

Member

fitzgen commented May 19, 2021

I don't think it is worth addressing at this time, because we just cut 1.0 and I don't think it is worth cutting a 2.0 just for this change.

Really unfortunate that this slipped through the cracks though :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment