-
Notifications
You must be signed in to change notification settings - Fork 61
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
Improve discoverability of OptionExt::ok_or_eyre
#130
Comments
This comment was marked as resolved.
This comment was marked as resolved.
OptionExt::unwrap_or_eyre
OptionExt::ok_or_eyre
This comment was marked as resolved.
This comment was marked as resolved.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the merge of #129, the new feature
option.ok_or_eyre("static error message")
was added toeyre
. This feature brings with it ergonomics parity withanyhow
.However, the feature is currently documented only under the "Compatibility with
anyhow
" section, whereOption
is discussed. This hampers discoverability.OptionExt::ok_or_eyre
's existence and usage should be documented more prominently inREADME.md
,eyre
crate-level documentation, and possibly (at release-time) published in articles(?) and / or social media posts.The text was updated successfully, but these errors were encountered: