-
Notifications
You must be signed in to change notification settings - Fork 92
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
Enforce unstable APIs can only be used if the related feature is enabled #2386
Enforce unstable APIs can only be used if the related feature is enabled #2386
Conversation
Co-authored-by: Zyad Hassan <88045115+zhassan-aws@users.noreply.github.com> Co-authored-by: Adrian Palacios <73246657+adpaco-aws@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Adding a debug assert when the unstable annotation is not parseable would be nice, but not necessary in this PR.
I just added in the last revision. :) |
- Break down check attribute function - Improve comment - Add debug_assert for invalid unstable attribute - Make all fields required
8ea47ab
to
9189813
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @celinval !
Co-authored-by: Adrian Palacios <73246657+adpaco-aws@users.noreply.github.com>
Description of changes:
This PR adds the new opt-in option for users to enable unstable features (via
-Z
option orunstable
table in Cargo.toml). This PR also adds logic to parse and verify APIs tagged withunstable
.Resolved issues:
Fixes #2357
Related RFC:
#2279
Call-outs:
Testing:
How is this change tested? New tests
Is this a refactor change? No
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.