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

Gate use of unstable try_trait_v2 feature #481

Closed

Conversation

nicholasbishop
Copy link
Contributor

Add a new enabled-by-default unstable_try_trait feature to the uefi
library to control whether the unstable try_trait_v2 rustc feature is
enabled.

It seems like there's still a fair amount of discussion around what the
Try API should look like in the tracking issue for try_trait_v2. This
could lead to the API being changed in the nightly compiler, and
breaking uefi-rs compilation (which is particularly annoying when using
a released version rather than the latest git version). Users who want
to avoid that problem can now disable unstable_try_trait.

#452

Add a new enabled-by-default `unstable_try_trait` feature to the `uefi`
library to control whether the unstable `try_trait_v2` rustc feature is
enabled.

It seems like there's still a fair amount of discussion around what the
Try API should look like in the tracking issue for try_trait_v2. This
could lead to the API being changed in the nightly compiler, and
breaking uefi-rs compilation (which is particularly annoying when using
a released version rather than the latest git version). Users who want
to avoid that problem can now disable `unstable_try_trait`.

rust-osdev#452
@phip1611
Copy link
Contributor

For the record, I'm in favor of #479.

I wrote my thoughts about breaking changes in uefi-rs here #495 (comment)

IMHO the small code changes of dropping this feature are not worth it to create possibly future technical debt (by keeping it, thus, having more complexity).

I do not insist on it and I'm open for discussions :)

@GabrielMajeri
Copy link
Collaborator

Yeah, I agree with what @phip1611 said. When I initially thought of the solution based on a feature gate, I didn't realize it would lead to so many small changes and still has downsides 😅

@nicholasbishop nicholasbishop deleted the bishop-feat-tryv2 branch September 1, 2022 21:14
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

Successfully merging this pull request may close these issues.

3 participants