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

Expose results rather than panicking #29

Open
mcandre opened this issue Nov 5, 2018 · 0 comments
Open

Expose results rather than panicking #29

mcandre opened this issue Nov 5, 2018 · 0 comments

Comments

@mcandre
Copy link
Owner

mcandre commented Nov 5, 2018

As a developer, I want more functions to return Result instead of panicking, so that I can react to errors more gracefully.

Expose more result values downstream rather than always panicking. This has the benefit of allowing more complex workflows. Would also present a more direct error message when results are unwrapped, instead of making it look like tinyrick is erroring.

At the extreme end of API openness, how to do this in a way that doesn't require so much .unwrap() boilerplate in the user's tinyrick.rs? Perhaps we could offer both panicking / implicitly unwrapping functions, as well as result-returning functions, similar to the exec! vs. exec_mut! macros.

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

No branches or pull requests

1 participant