-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
stabilize const_int_pow #76829
stabilize const_int_pow #76829
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
This PR stabilized const for the following public methods:
|
r? @KodrAus to kick off libs FCP here, diff in PR looks good from an impl perspective |
☔ The latest upstream changes (presumably #76327) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
26d50cb
to
5070d51
Compare
☔ The latest upstream changes (presumably #76850) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
5070d51
to
7db7b41
Compare
7db7b41
to
4a062a1
Compare
I've just force-pushed an update with the since field set to |
@rfcbot fcp merge See: #76829 (comment) This stabilizes a few more cc @rust-lang/wg-const-eval |
Team member @KodrAus has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
☔ The latest upstream changes (presumably #79167) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
@bors r- yea, please adjust the stabilization date, too |
4a062a1
to
a6bcf7a
Compare
Done. |
@bors r+ |
📌 Commit a6bcf7a has been approved by |
⌛ Testing commit a6bcf7a with merge b1801ff6fe6c747687a9e423da6fda1d0c736835... |
💔 Test failed - checks-actions |
@bors retry gzip failures in CI |
…as-schievink Rollup of 10 pull requests Successful merges: - rust-lang#76829 (stabilize const_int_pow) - rust-lang#79080 (MIR visitor: Don't treat debuginfo field access as a use of the struct) - rust-lang#79236 (const_generics: assert resolve hack causes an error) - rust-lang#79287 (Allow using generic trait methods in `const fn`) - rust-lang#79324 (Use Option::and_then instead of open-coding it) - rust-lang#79325 (Reduce boilerplate with the `?` operator) - rust-lang#79330 (Fix typo in comment) - rust-lang#79333 (doc typo) - rust-lang#79337 (Use Option::map instead of open coding it) - rust-lang#79343 (Add my (`@flip1995)` work mail to the mailmap) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
const_int_pow was stabilized in Rust 1.50.0 rust-lang/rust#76829
const_int_pow was stabilized in Rust 1.50.0 rust-lang/rust#76829
const_int_pow was stabilized in Rust 1.50.0 rust-lang/rust#76829
const_int_pow was stabilized in Rust 1.50.0 rust-lang/rust#76829
const_int_pow was stabilized in Rust 1.50.0 rust-lang/rust#76829
const_int_pow was stabilized in Rust 1.50.0 rust-lang/rust#76829
This also requires stabilizing constctlz for const ctlz_nonzero.