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

Remove error_in_core feature #799

Closed
haerdib opened this issue Sep 2, 2024 · 5 comments · Fixed by #803
Closed

Remove error_in_core feature #799

haerdib opened this issue Sep 2, 2024 · 5 comments · Fixed by #803
Assignees

Comments

@haerdib
Copy link
Contributor

haerdib commented Sep 2, 2024

Error should now be implemented fully in core, so there should be no need for this feature anymore.

Related issue: rust-lang/rust#103765

@Niederb
Copy link
Contributor

Niederb commented Sep 2, 2024

If I remember correctly this is the last feature that prevents us from switching to a stable Rust version. So we could try switching to stable.

@haerdib haerdib self-assigned this Sep 3, 2024
@haerdib
Copy link
Contributor Author

haerdib commented Sep 3, 2024

Good idea, feature will be stabilized in 2 days (on the 5th September). So let's wait until then and see if we can use the stable toolchain.

@haerdib
Copy link
Contributor Author

haerdib commented Sep 11, 2024

Switchin to stable is currently not possible (or requires quite some effort) because of our no_std check. There, we require the following features:

#![feature(start, libc, lang_items)]
#![feature(alloc_error_handler)]

At least for the alloc_error_handler there does not seem to be an easy alternative: rust-lang/rust#51540

I did a quick research to see if there's a better alternative for no_stds check but I didn't really find one. cargo-nono did not install with cargo install cargo-nono and it was updated last 4 years ago, it doesn't really seem a good alternative.

So I think it's currenlty not worth it to switch to stable.

@masapr
Copy link
Collaborator

masapr commented Sep 12, 2024

So we should move the feature to the icebox?

@haerdib
Copy link
Contributor Author

haerdib commented Sep 12, 2024

No, the error_in_core feature can still be removed. Only the switch to stable toolchain is not easily possible. PR #803 will close this issue.

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

Successfully merging a pull request may close this issue.

3 participants