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

Why is #[no_std] mentioned in the documentation if there is no std feature anymore? #89

Closed
K4rakara opened this issue Dec 5, 2022 · 2 comments
Assignees

Comments

@K4rakara
Copy link

K4rakara commented Dec 5, 2022

Title mostly. In PR #29 #[no_std] support was removed from the library, but not from the docs.

thenorili added a commit to thenorili/eyre that referenced this issue Nov 5, 2023
no_std support was removed in 2020 with PR eyre-rs#29. This change updates the documentation to reflect that as suggested in PR eyre-rs#89. It still mentions no_std, which will hopefully keep it on our minds enough to check sometimes and see if the upstream problem has been resolved.
yaahc added a commit that referenced this issue Nov 7, 2023
no_std support was removed in 2020 with PR #29. This change updates the documentation to reflect that as suggested in PR #89. It still mentions no_std, which will hopefully keep it on our minds enough to check sometimes and see if the upstream problem has been resolved.

Co-authored-by: Jane Losare-Lusby <[email protected]>
@thenorili
Copy link
Contributor

Thanks for pointing this out =] With your help this issue has been resolved!

@thenorili thenorili self-assigned this Nov 20, 2023
@thenorili
Copy link
Contributor

Completed in #111

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

2 participants