In Option::get_or_insert_with(), forget the None instead of dropping it. - #148562

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop
Mar 10, 2026
Merged

In Option::get_or_insert_with(), forget the None instead of dropping it.#148562
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop

Conversation

@kpreid

@kpreidkpreid commented Nov 6, 2025

Copy link
Copy Markdown
Contributor

View all comments

Per #148486 (comment)

In Option::get_or_insert_with(), after replacing the None with Some, forget the None instead of dropping it.

This allows eliminating the T: [const] Destruct bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit drop_in_place::<Option<T>>() that will never do anything (and which might even persist after optimization).

@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @ibraheemdev

rustbot has assigned @ibraheemdev.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@kpreid

Copy link
Copy Markdown
ContributorAuthor

cc @cyb0124 (this change is based on their idea)

Comment threadlibrary/coretests/tests/option.rs Outdated
Comment threadlibrary/core/src/option.rs Outdated
@kpreid
kpreidforce-pushed the get-init-drop branch 2 times, most recently from ecc05f4 to 2e71187CompareNovember 6, 2025 23:31

@hkBsthkBst left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Looks good to me.

View changes since this review

Comment threadlibrary/core/src/option.rs Outdated
…ing it.
This allows eliminating the `T: [const] Destruct` bounds and avoids
generating an implicit `drop_in_place::<Option<T>>()` that will never do
anything.
Ideally, the compiler would prove that that drop is not necessary
itself, but it currently doesn't, even with `const_precise_live_drops`
enabled.
@ibraheemdev

Copy link
Copy Markdown
Member

The implementation looks good to me. r? libs-api for the unstable API change.

@rustbotrustbot added the T-libs-api [DEPRECATED; DO NOT USE] label Feb 9, 2026
@rustbotrustbot assigned the8472 and unassigned ibraheemdevFeb 9, 2026
@kpreid

kpreid commented Mar 9, 2026

Copy link
Copy Markdown
ContributorAuthor

Per advice:

@rustbot label -S-waiting-on-review +S-waiting-on-t-libs-api

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: S-waiting-on-libs-api

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@rustbotrustbot added S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 9, 2026
@oli-obk

Copy link
Copy Markdown
Contributor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

Also wondering about this pattern in general. Seems like sth const precise live drops could also handle, haven't looked at that in forever so I don't remember the details of it.

Anyway, if the final runtime MIR looks good, let's merge this

@kpreid

Copy link
Copy Markdown
ContributorAuthor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

I’m not familiar with how to do that, but I will look into it.

Seems like sth const precise live drops could also handle,

See prior discussion #148562 (comment) — in brief, having const_precise_live_drops would mean we are having the compiler doing static checking on how control flow affects values (whether the option is None), which is something that we generally only do for lint (e.g. if false {} is not counted as unreachable code).

@kpreid

Copy link
Copy Markdown
ContributorAuthor

oli-obk and I have looked at the MIR through dropping both implementations into Compiler Explorer and it seems generally similar, but also not very optimized either before or after.

@rustbot label +const-hack

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: const-hack

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@oli-obk

Copy link
Copy Markdown
Contributor

@bors r+ rollup

r? @oli-obk

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

📋 This PR cannot be approved because it currently has the following label: S-waiting-on-t-libs-api.

@rustbotrustbot assigned oli-obk and unassigned the8472Mar 9, 2026
@ChrisDentonChrisDenton removed the S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] label Mar 9, 2026
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per rust-lang#148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@matthiaskrgr

Copy link
Copy Markdown
Member

@bors yield

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153628.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
Rollup of 8 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #149931 (rustdoc: don't give depreciation notes special handling)
- #153608 (ast_passes: unsupported arch w/ scalable vectors)
- #153609 (Add missing `Diag::with_span_suggestion_with_style` method)
- #153610 (Only lint unused features if they are unstable)
- #153616 (Update `sysinfo` version to `0.38.4`)
- #153619 (Update books)
- #153624 (Ping fmease on parser modifications)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@Zalathar

Copy link
Copy Markdown
Member

The dist-x86_64-linux job is stuck.

@bors yield

@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153631.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@rust-borsrust-borsBot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 10, 2026
@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 8744ff0 failed: CI. Failed job:

@Zalathar

Copy link
Copy Markdown
Member

@bors retry (network failure)

@rust-borsrust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 10, 2026
rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

A job failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)
/dev/sda15 105M 6.2M 99M 6% /boot/efi
tmpfs 1.6G 12K 1.6G 1% /run/user/1001
================================================================================
Sufficient disk space available (95001912KB >= 52428800KB). Skipping cleanup.
##[group]Run src/ci/scripts/setup-environment.sh
src/ci/scripts/setup-environment.sh
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors
rust-borsBot merged commit ce97229 into rust-lang:mainMar 10, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 10, 2026
rust-timer added a commit that referenced this pull request Mar 10, 2026
Rollup merge of #148562 - kpreid:get-init-drop, r=oli-obk
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@kpreid
kpreid deleted the get-init-drop branch March 10, 2026 20:40
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
Rollup of 4 pull requests
Successful merges:
- rust-lang/rust#148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- rust-lang/rust#153325 (tests/ui/cfg: add annotations for reference rules)
- rust-lang/rust#153621 (Remove `TyCtxt::node_span_lint` method)
- rust-lang/rust#153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-libsRelevant to the library team, which will review and decide on the PR/issue.T-libs-api[DEPRECATED; DO NOT USE]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@kpreid@rustbot@ibraheemdev@oli-obk@ChrisDenton@matthiaskrgr@Zalathar@rust-log-analyzer@clarfonthey@hkBst@the8472
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

In Option::get_or_insert_with(), forget the None instead of dropping it. - #148562

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop
Mar 10, 2026
Merged

In Option::get_or_insert_with(), forget the None instead of dropping it.#148562
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop

Conversation

@kpreid

@kpreidkpreid commented Nov 6, 2025

Copy link
Copy Markdown
Contributor

View all comments

Per #148486 (comment)

In Option::get_or_insert_with(), after replacing the None with Some, forget the None instead of dropping it.

This allows eliminating the T: [const] Destruct bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit drop_in_place::<Option<T>>() that will never do anything (and which might even persist after optimization).

@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @ibraheemdev

rustbot has assigned @ibraheemdev.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@kpreid

Copy link
Copy Markdown
ContributorAuthor

cc @cyb0124 (this change is based on their idea)

Comment threadlibrary/coretests/tests/option.rs Outdated
Comment threadlibrary/core/src/option.rs Outdated
@kpreid
kpreidforce-pushed the get-init-drop branch 2 times, most recently from ecc05f4 to 2e71187CompareNovember 6, 2025 23:31

@hkBsthkBst left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Looks good to me.

View changes since this review

Comment threadlibrary/core/src/option.rs Outdated
…ing it.
This allows eliminating the `T: [const] Destruct` bounds and avoids
generating an implicit `drop_in_place::<Option<T>>()` that will never do
anything.
Ideally, the compiler would prove that that drop is not necessary
itself, but it currently doesn't, even with `const_precise_live_drops`
enabled.
@ibraheemdev

Copy link
Copy Markdown
Member

The implementation looks good to me. r? libs-api for the unstable API change.

@rustbotrustbot added the T-libs-api [DEPRECATED; DO NOT USE] label Feb 9, 2026
@rustbotrustbot assigned the8472 and unassigned ibraheemdevFeb 9, 2026
@kpreid

kpreid commented Mar 9, 2026

Copy link
Copy Markdown
ContributorAuthor

Per advice:

@rustbot label -S-waiting-on-review +S-waiting-on-t-libs-api

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: S-waiting-on-libs-api

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@rustbotrustbot added S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 9, 2026
@oli-obk

Copy link
Copy Markdown
Contributor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

Also wondering about this pattern in general. Seems like sth const precise live drops could also handle, haven't looked at that in forever so I don't remember the details of it.

Anyway, if the final runtime MIR looks good, let's merge this

@kpreid

Copy link
Copy Markdown
ContributorAuthor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

I’m not familiar with how to do that, but I will look into it.

Seems like sth const precise live drops could also handle,

See prior discussion #148562 (comment) — in brief, having const_precise_live_drops would mean we are having the compiler doing static checking on how control flow affects values (whether the option is None), which is something that we generally only do for lint (e.g. if false {} is not counted as unreachable code).

@kpreid

Copy link
Copy Markdown
ContributorAuthor

oli-obk and I have looked at the MIR through dropping both implementations into Compiler Explorer and it seems generally similar, but also not very optimized either before or after.

@rustbot label +const-hack

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: const-hack

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@oli-obk

Copy link
Copy Markdown
Contributor

@bors r+ rollup

r? @oli-obk

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

📋 This PR cannot be approved because it currently has the following label: S-waiting-on-t-libs-api.

@rustbotrustbot assigned oli-obk and unassigned the8472Mar 9, 2026
@ChrisDentonChrisDenton removed the S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] label Mar 9, 2026
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per rust-lang#148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@matthiaskrgr

Copy link
Copy Markdown
Member

@bors yield

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153628.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
Rollup of 8 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #149931 (rustdoc: don't give depreciation notes special handling)
- #153608 (ast_passes: unsupported arch w/ scalable vectors)
- #153609 (Add missing `Diag::with_span_suggestion_with_style` method)
- #153610 (Only lint unused features if they are unstable)
- #153616 (Update `sysinfo` version to `0.38.4`)
- #153619 (Update books)
- #153624 (Ping fmease on parser modifications)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@Zalathar

Copy link
Copy Markdown
Member

The dist-x86_64-linux job is stuck.

@bors yield

@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153631.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@rust-borsrust-borsBot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 10, 2026
@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 8744ff0 failed: CI. Failed job:

@Zalathar

Copy link
Copy Markdown
Member

@bors retry (network failure)

@rust-borsrust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 10, 2026
rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

A job failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)
/dev/sda15 105M 6.2M 99M 6% /boot/efi
tmpfs 1.6G 12K 1.6G 1% /run/user/1001
================================================================================
Sufficient disk space available (95001912KB >= 52428800KB). Skipping cleanup.
##[group]Run src/ci/scripts/setup-environment.sh
src/ci/scripts/setup-environment.sh
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors
rust-borsBot merged commit ce97229 into rust-lang:mainMar 10, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 10, 2026
rust-timer added a commit that referenced this pull request Mar 10, 2026
Rollup merge of #148562 - kpreid:get-init-drop, r=oli-obk
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@kpreid
kpreid deleted the get-init-drop branch March 10, 2026 20:40
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
Rollup of 4 pull requests
Successful merges:
- rust-lang/rust#148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- rust-lang/rust#153325 (tests/ui/cfg: add annotations for reference rules)
- rust-lang/rust#153621 (Remove `TyCtxt::node_span_lint` method)
- rust-lang/rust#153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-libsRelevant to the library team, which will review and decide on the PR/issue.T-libs-api[DEPRECATED; DO NOT USE]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@kpreid@rustbot@ibraheemdev@oli-obk@ChrisDenton@matthiaskrgr@Zalathar@rust-log-analyzer@clarfonthey@hkBst@the8472
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

In Option::get_or_insert_with(), forget the None instead of dropping it. - #148562

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop
Mar 10, 2026
Merged

In Option::get_or_insert_with(), forget the None instead of dropping it.#148562
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop

Conversation

@kpreid

@kpreidkpreid commented Nov 6, 2025

Copy link
Copy Markdown
Contributor

View all comments

Per #148486 (comment)

In Option::get_or_insert_with(), after replacing the None with Some, forget the None instead of dropping it.

This allows eliminating the T: [const] Destruct bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit drop_in_place::<Option<T>>() that will never do anything (and which might even persist after optimization).

@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @ibraheemdev

rustbot has assigned @ibraheemdev.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@kpreid

Copy link
Copy Markdown
ContributorAuthor

cc @cyb0124 (this change is based on their idea)

Comment threadlibrary/coretests/tests/option.rs Outdated
Comment threadlibrary/core/src/option.rs Outdated
@kpreid
kpreidforce-pushed the get-init-drop branch 2 times, most recently from ecc05f4 to 2e71187CompareNovember 6, 2025 23:31

@hkBsthkBst left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Looks good to me.

View changes since this review

Comment threadlibrary/core/src/option.rs Outdated
…ing it.
This allows eliminating the `T: [const] Destruct` bounds and avoids
generating an implicit `drop_in_place::<Option<T>>()` that will never do
anything.
Ideally, the compiler would prove that that drop is not necessary
itself, but it currently doesn't, even with `const_precise_live_drops`
enabled.
@ibraheemdev

Copy link
Copy Markdown
Member

The implementation looks good to me. r? libs-api for the unstable API change.

@rustbotrustbot added the T-libs-api [DEPRECATED; DO NOT USE] label Feb 9, 2026
@rustbotrustbot assigned the8472 and unassigned ibraheemdevFeb 9, 2026
@kpreid

kpreid commented Mar 9, 2026

Copy link
Copy Markdown
ContributorAuthor

Per advice:

@rustbot label -S-waiting-on-review +S-waiting-on-t-libs-api

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: S-waiting-on-libs-api

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@rustbotrustbot added S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 9, 2026
@oli-obk

Copy link
Copy Markdown
Contributor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

Also wondering about this pattern in general. Seems like sth const precise live drops could also handle, haven't looked at that in forever so I don't remember the details of it.

Anyway, if the final runtime MIR looks good, let's merge this

@kpreid

Copy link
Copy Markdown
ContributorAuthor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

I’m not familiar with how to do that, but I will look into it.

Seems like sth const precise live drops could also handle,

See prior discussion #148562 (comment) — in brief, having const_precise_live_drops would mean we are having the compiler doing static checking on how control flow affects values (whether the option is None), which is something that we generally only do for lint (e.g. if false {} is not counted as unreachable code).

@kpreid

Copy link
Copy Markdown
ContributorAuthor

oli-obk and I have looked at the MIR through dropping both implementations into Compiler Explorer and it seems generally similar, but also not very optimized either before or after.

@rustbot label +const-hack

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: const-hack

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@oli-obk

Copy link
Copy Markdown
Contributor

@bors r+ rollup

r? @oli-obk

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

📋 This PR cannot be approved because it currently has the following label: S-waiting-on-t-libs-api.

@rustbotrustbot assigned oli-obk and unassigned the8472Mar 9, 2026
@ChrisDentonChrisDenton removed the S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] label Mar 9, 2026
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per rust-lang#148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@matthiaskrgr

Copy link
Copy Markdown
Member

@bors yield

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153628.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
Rollup of 8 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #149931 (rustdoc: don't give depreciation notes special handling)
- #153608 (ast_passes: unsupported arch w/ scalable vectors)
- #153609 (Add missing `Diag::with_span_suggestion_with_style` method)
- #153610 (Only lint unused features if they are unstable)
- #153616 (Update `sysinfo` version to `0.38.4`)
- #153619 (Update books)
- #153624 (Ping fmease on parser modifications)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@Zalathar

Copy link
Copy Markdown
Member

The dist-x86_64-linux job is stuck.

@bors yield

@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153631.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@rust-borsrust-borsBot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 10, 2026
@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 8744ff0 failed: CI. Failed job:

@Zalathar

Copy link
Copy Markdown
Member

@bors retry (network failure)

@rust-borsrust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 10, 2026
rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

A job failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)
/dev/sda15 105M 6.2M 99M 6% /boot/efi
tmpfs 1.6G 12K 1.6G 1% /run/user/1001
================================================================================
Sufficient disk space available (95001912KB >= 52428800KB). Skipping cleanup.
##[group]Run src/ci/scripts/setup-environment.sh
src/ci/scripts/setup-environment.sh
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors
rust-borsBot merged commit ce97229 into rust-lang:mainMar 10, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 10, 2026
rust-timer added a commit that referenced this pull request Mar 10, 2026
Rollup merge of #148562 - kpreid:get-init-drop, r=oli-obk
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@kpreid
kpreid deleted the get-init-drop branch March 10, 2026 20:40
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
Rollup of 4 pull requests
Successful merges:
- rust-lang/rust#148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- rust-lang/rust#153325 (tests/ui/cfg: add annotations for reference rules)
- rust-lang/rust#153621 (Remove `TyCtxt::node_span_lint` method)
- rust-lang/rust#153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-libsRelevant to the library team, which will review and decide on the PR/issue.T-libs-api[DEPRECATED; DO NOT USE]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@kpreid@rustbot@ibraheemdev@oli-obk@ChrisDenton@matthiaskrgr@Zalathar@rust-log-analyzer@clarfonthey@hkBst@the8472
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

In Option::get_or_insert_with(), forget the None instead of dropping it. - #148562

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop
Mar 10, 2026
Merged

In Option::get_or_insert_with(), forget the None instead of dropping it.#148562
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop

Conversation

@kpreid

@kpreidkpreid commented Nov 6, 2025

Copy link
Copy Markdown
Contributor

View all comments

Per #148486 (comment)

In Option::get_or_insert_with(), after replacing the None with Some, forget the None instead of dropping it.

This allows eliminating the T: [const] Destruct bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit drop_in_place::<Option<T>>() that will never do anything (and which might even persist after optimization).

@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @ibraheemdev

rustbot has assigned @ibraheemdev.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@kpreid

Copy link
Copy Markdown
ContributorAuthor

cc @cyb0124 (this change is based on their idea)

Comment threadlibrary/coretests/tests/option.rs Outdated
Comment threadlibrary/core/src/option.rs Outdated
@kpreid
kpreidforce-pushed the get-init-drop branch 2 times, most recently from ecc05f4 to 2e71187CompareNovember 6, 2025 23:31

@hkBsthkBst left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Looks good to me.

View changes since this review

Comment threadlibrary/core/src/option.rs Outdated
…ing it.
This allows eliminating the `T: [const] Destruct` bounds and avoids
generating an implicit `drop_in_place::<Option<T>>()` that will never do
anything.
Ideally, the compiler would prove that that drop is not necessary
itself, but it currently doesn't, even with `const_precise_live_drops`
enabled.
@ibraheemdev

Copy link
Copy Markdown
Member

The implementation looks good to me. r? libs-api for the unstable API change.

@rustbotrustbot added the T-libs-api [DEPRECATED; DO NOT USE] label Feb 9, 2026
@rustbotrustbot assigned the8472 and unassigned ibraheemdevFeb 9, 2026
@kpreid

kpreid commented Mar 9, 2026

Copy link
Copy Markdown
ContributorAuthor

Per advice:

@rustbot label -S-waiting-on-review +S-waiting-on-t-libs-api

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: S-waiting-on-libs-api

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@rustbotrustbot added S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 9, 2026
@oli-obk

Copy link
Copy Markdown
Contributor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

Also wondering about this pattern in general. Seems like sth const precise live drops could also handle, haven't looked at that in forever so I don't remember the details of it.

Anyway, if the final runtime MIR looks good, let's merge this

@kpreid

Copy link
Copy Markdown
ContributorAuthor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

I’m not familiar with how to do that, but I will look into it.

Seems like sth const precise live drops could also handle,

See prior discussion #148562 (comment) — in brief, having const_precise_live_drops would mean we are having the compiler doing static checking on how control flow affects values (whether the option is None), which is something that we generally only do for lint (e.g. if false {} is not counted as unreachable code).

@kpreid

Copy link
Copy Markdown
ContributorAuthor

oli-obk and I have looked at the MIR through dropping both implementations into Compiler Explorer and it seems generally similar, but also not very optimized either before or after.

@rustbot label +const-hack

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: const-hack

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@oli-obk

Copy link
Copy Markdown
Contributor

@bors r+ rollup

r? @oli-obk

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

📋 This PR cannot be approved because it currently has the following label: S-waiting-on-t-libs-api.

@rustbotrustbot assigned oli-obk and unassigned the8472Mar 9, 2026
@ChrisDentonChrisDenton removed the S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] label Mar 9, 2026
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per rust-lang#148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@matthiaskrgr

Copy link
Copy Markdown
Member

@bors yield

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153628.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
Rollup of 8 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #149931 (rustdoc: don't give depreciation notes special handling)
- #153608 (ast_passes: unsupported arch w/ scalable vectors)
- #153609 (Add missing `Diag::with_span_suggestion_with_style` method)
- #153610 (Only lint unused features if they are unstable)
- #153616 (Update `sysinfo` version to `0.38.4`)
- #153619 (Update books)
- #153624 (Ping fmease on parser modifications)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@Zalathar

Copy link
Copy Markdown
Member

The dist-x86_64-linux job is stuck.

@bors yield

@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153631.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@rust-borsrust-borsBot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 10, 2026
@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 8744ff0 failed: CI. Failed job:

@Zalathar

Copy link
Copy Markdown
Member

@bors retry (network failure)

@rust-borsrust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 10, 2026
rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

A job failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)
/dev/sda15 105M 6.2M 99M 6% /boot/efi
tmpfs 1.6G 12K 1.6G 1% /run/user/1001
================================================================================
Sufficient disk space available (95001912KB >= 52428800KB). Skipping cleanup.
##[group]Run src/ci/scripts/setup-environment.sh
src/ci/scripts/setup-environment.sh
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors
rust-borsBot merged commit ce97229 into rust-lang:mainMar 10, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 10, 2026
rust-timer added a commit that referenced this pull request Mar 10, 2026
Rollup merge of #148562 - kpreid:get-init-drop, r=oli-obk
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@kpreid
kpreid deleted the get-init-drop branch March 10, 2026 20:40
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
Rollup of 4 pull requests
Successful merges:
- rust-lang/rust#148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- rust-lang/rust#153325 (tests/ui/cfg: add annotations for reference rules)
- rust-lang/rust#153621 (Remove `TyCtxt::node_span_lint` method)
- rust-lang/rust#153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-libsRelevant to the library team, which will review and decide on the PR/issue.T-libs-api[DEPRECATED; DO NOT USE]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@kpreid@rustbot@ibraheemdev@oli-obk@ChrisDenton@matthiaskrgr@Zalathar@rust-log-analyzer@clarfonthey@hkBst@the8472
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

In Option::get_or_insert_with(), forget the None instead of dropping it. - #148562

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop
Mar 10, 2026
Merged

In Option::get_or_insert_with(), forget the None instead of dropping it.#148562
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop

Conversation

@kpreid

@kpreidkpreid commented Nov 6, 2025

Copy link
Copy Markdown
Contributor

View all comments

Per #148486 (comment)

In Option::get_or_insert_with(), after replacing the None with Some, forget the None instead of dropping it.

This allows eliminating the T: [const] Destruct bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit drop_in_place::<Option<T>>() that will never do anything (and which might even persist after optimization).

@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @ibraheemdev

rustbot has assigned @ibraheemdev.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@kpreid

Copy link
Copy Markdown
ContributorAuthor

cc @cyb0124 (this change is based on their idea)

Comment threadlibrary/coretests/tests/option.rs Outdated
Comment threadlibrary/core/src/option.rs Outdated
@kpreid
kpreidforce-pushed the get-init-drop branch 2 times, most recently from ecc05f4 to 2e71187CompareNovember 6, 2025 23:31

@hkBsthkBst left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Looks good to me.

View changes since this review

Comment threadlibrary/core/src/option.rs Outdated
…ing it.
This allows eliminating the `T: [const] Destruct` bounds and avoids
generating an implicit `drop_in_place::<Option<T>>()` that will never do
anything.
Ideally, the compiler would prove that that drop is not necessary
itself, but it currently doesn't, even with `const_precise_live_drops`
enabled.
@ibraheemdev

Copy link
Copy Markdown
Member

The implementation looks good to me. r? libs-api for the unstable API change.

@rustbotrustbot added the T-libs-api [DEPRECATED; DO NOT USE] label Feb 9, 2026
@rustbotrustbot assigned the8472 and unassigned ibraheemdevFeb 9, 2026
@kpreid

kpreid commented Mar 9, 2026

Copy link
Copy Markdown
ContributorAuthor

Per advice:

@rustbot label -S-waiting-on-review +S-waiting-on-t-libs-api

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: S-waiting-on-libs-api

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@rustbotrustbot added S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 9, 2026
@oli-obk

Copy link
Copy Markdown
Contributor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

Also wondering about this pattern in general. Seems like sth const precise live drops could also handle, haven't looked at that in forever so I don't remember the details of it.

Anyway, if the final runtime MIR looks good, let's merge this

@kpreid

Copy link
Copy Markdown
ContributorAuthor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

I’m not familiar with how to do that, but I will look into it.

Seems like sth const precise live drops could also handle,

See prior discussion #148562 (comment) — in brief, having const_precise_live_drops would mean we are having the compiler doing static checking on how control flow affects values (whether the option is None), which is something that we generally only do for lint (e.g. if false {} is not counted as unreachable code).

@kpreid

Copy link
Copy Markdown
ContributorAuthor

oli-obk and I have looked at the MIR through dropping both implementations into Compiler Explorer and it seems generally similar, but also not very optimized either before or after.

@rustbot label +const-hack

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: const-hack

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@oli-obk

Copy link
Copy Markdown
Contributor

@bors r+ rollup

r? @oli-obk

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

📋 This PR cannot be approved because it currently has the following label: S-waiting-on-t-libs-api.

@rustbotrustbot assigned oli-obk and unassigned the8472Mar 9, 2026
@ChrisDentonChrisDenton removed the S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] label Mar 9, 2026
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per rust-lang#148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@matthiaskrgr

Copy link
Copy Markdown
Member

@bors yield

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153628.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
Rollup of 8 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #149931 (rustdoc: don't give depreciation notes special handling)
- #153608 (ast_passes: unsupported arch w/ scalable vectors)
- #153609 (Add missing `Diag::with_span_suggestion_with_style` method)
- #153610 (Only lint unused features if they are unstable)
- #153616 (Update `sysinfo` version to `0.38.4`)
- #153619 (Update books)
- #153624 (Ping fmease on parser modifications)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@Zalathar

Copy link
Copy Markdown
Member

The dist-x86_64-linux job is stuck.

@bors yield

@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153631.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@rust-borsrust-borsBot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 10, 2026
@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 8744ff0 failed: CI. Failed job:

@Zalathar

Copy link
Copy Markdown
Member

@bors retry (network failure)

@rust-borsrust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 10, 2026
rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

A job failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)
/dev/sda15 105M 6.2M 99M 6% /boot/efi
tmpfs 1.6G 12K 1.6G 1% /run/user/1001
================================================================================
Sufficient disk space available (95001912KB >= 52428800KB). Skipping cleanup.
##[group]Run src/ci/scripts/setup-environment.sh
src/ci/scripts/setup-environment.sh
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors
rust-borsBot merged commit ce97229 into rust-lang:mainMar 10, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 10, 2026
rust-timer added a commit that referenced this pull request Mar 10, 2026
Rollup merge of #148562 - kpreid:get-init-drop, r=oli-obk
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@kpreid
kpreid deleted the get-init-drop branch March 10, 2026 20:40
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
Rollup of 4 pull requests
Successful merges:
- rust-lang/rust#148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- rust-lang/rust#153325 (tests/ui/cfg: add annotations for reference rules)
- rust-lang/rust#153621 (Remove `TyCtxt::node_span_lint` method)
- rust-lang/rust#153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-libsRelevant to the library team, which will review and decide on the PR/issue.T-libs-api[DEPRECATED; DO NOT USE]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@kpreid@rustbot@ibraheemdev@oli-obk@ChrisDenton@matthiaskrgr@Zalathar@rust-log-analyzer@clarfonthey@hkBst@the8472
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

In Option::get_or_insert_with(), forget the None instead of dropping it. - #148562

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop
Mar 10, 2026
Merged

In Option::get_or_insert_with(), forget the None instead of dropping it.#148562
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop

Conversation

@kpreid

@kpreidkpreid commented Nov 6, 2025

Copy link
Copy Markdown
Contributor

View all comments

Per #148486 (comment)

In Option::get_or_insert_with(), after replacing the None with Some, forget the None instead of dropping it.

This allows eliminating the T: [const] Destruct bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit drop_in_place::<Option<T>>() that will never do anything (and which might even persist after optimization).

@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @ibraheemdev

rustbot has assigned @ibraheemdev.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@kpreid

Copy link
Copy Markdown
ContributorAuthor

cc @cyb0124 (this change is based on their idea)

Comment threadlibrary/coretests/tests/option.rs Outdated
Comment threadlibrary/core/src/option.rs Outdated
@kpreid
kpreidforce-pushed the get-init-drop branch 2 times, most recently from ecc05f4 to 2e71187CompareNovember 6, 2025 23:31

@hkBsthkBst left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Looks good to me.

View changes since this review

Comment threadlibrary/core/src/option.rs Outdated
…ing it.
This allows eliminating the `T: [const] Destruct` bounds and avoids
generating an implicit `drop_in_place::<Option<T>>()` that will never do
anything.
Ideally, the compiler would prove that that drop is not necessary
itself, but it currently doesn't, even with `const_precise_live_drops`
enabled.
@ibraheemdev

Copy link
Copy Markdown
Member

The implementation looks good to me. r? libs-api for the unstable API change.

@rustbotrustbot added the T-libs-api [DEPRECATED; DO NOT USE] label Feb 9, 2026
@rustbotrustbot assigned the8472 and unassigned ibraheemdevFeb 9, 2026
@kpreid

kpreid commented Mar 9, 2026

Copy link
Copy Markdown
ContributorAuthor

Per advice:

@rustbot label -S-waiting-on-review +S-waiting-on-t-libs-api

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: S-waiting-on-libs-api

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@rustbotrustbot added S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 9, 2026
@oli-obk

Copy link
Copy Markdown
Contributor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

Also wondering about this pattern in general. Seems like sth const precise live drops could also handle, haven't looked at that in forever so I don't remember the details of it.

Anyway, if the final runtime MIR looks good, let's merge this

@kpreid

Copy link
Copy Markdown
ContributorAuthor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

I’m not familiar with how to do that, but I will look into it.

Seems like sth const precise live drops could also handle,

See prior discussion #148562 (comment) — in brief, having const_precise_live_drops would mean we are having the compiler doing static checking on how control flow affects values (whether the option is None), which is something that we generally only do for lint (e.g. if false {} is not counted as unreachable code).

@kpreid

Copy link
Copy Markdown
ContributorAuthor

oli-obk and I have looked at the MIR through dropping both implementations into Compiler Explorer and it seems generally similar, but also not very optimized either before or after.

@rustbot label +const-hack

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: const-hack

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@oli-obk

Copy link
Copy Markdown
Contributor

@bors r+ rollup

r? @oli-obk

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

📋 This PR cannot be approved because it currently has the following label: S-waiting-on-t-libs-api.

@rustbotrustbot assigned oli-obk and unassigned the8472Mar 9, 2026
@ChrisDentonChrisDenton removed the S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] label Mar 9, 2026
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per rust-lang#148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@matthiaskrgr

Copy link
Copy Markdown
Member

@bors yield

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153628.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
Rollup of 8 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #149931 (rustdoc: don't give depreciation notes special handling)
- #153608 (ast_passes: unsupported arch w/ scalable vectors)
- #153609 (Add missing `Diag::with_span_suggestion_with_style` method)
- #153610 (Only lint unused features if they are unstable)
- #153616 (Update `sysinfo` version to `0.38.4`)
- #153619 (Update books)
- #153624 (Ping fmease on parser modifications)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@Zalathar

Copy link
Copy Markdown
Member

The dist-x86_64-linux job is stuck.

@bors yield

@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153631.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@rust-borsrust-borsBot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 10, 2026
@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 8744ff0 failed: CI. Failed job:

@Zalathar

Copy link
Copy Markdown
Member

@bors retry (network failure)

@rust-borsrust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 10, 2026
rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

A job failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)
/dev/sda15 105M 6.2M 99M 6% /boot/efi
tmpfs 1.6G 12K 1.6G 1% /run/user/1001
================================================================================
Sufficient disk space available (95001912KB >= 52428800KB). Skipping cleanup.
##[group]Run src/ci/scripts/setup-environment.sh
src/ci/scripts/setup-environment.sh
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors
rust-borsBot merged commit ce97229 into rust-lang:mainMar 10, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 10, 2026
rust-timer added a commit that referenced this pull request Mar 10, 2026
Rollup merge of #148562 - kpreid:get-init-drop, r=oli-obk
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@kpreid
kpreid deleted the get-init-drop branch March 10, 2026 20:40
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
Rollup of 4 pull requests
Successful merges:
- rust-lang/rust#148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- rust-lang/rust#153325 (tests/ui/cfg: add annotations for reference rules)
- rust-lang/rust#153621 (Remove `TyCtxt::node_span_lint` method)
- rust-lang/rust#153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-libsRelevant to the library team, which will review and decide on the PR/issue.T-libs-api[DEPRECATED; DO NOT USE]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@kpreid@rustbot@ibraheemdev@oli-obk@ChrisDenton@matthiaskrgr@Zalathar@rust-log-analyzer@clarfonthey@hkBst@the8472
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

In Option::get_or_insert_with(), forget the None instead of dropping it. - #148562

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop
Mar 10, 2026
Merged

In Option::get_or_insert_with(), forget the None instead of dropping it.#148562
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop

Conversation

@kpreid

@kpreidkpreid commented Nov 6, 2025

Copy link
Copy Markdown
Contributor

View all comments

Per #148486 (comment)

In Option::get_or_insert_with(), after replacing the None with Some, forget the None instead of dropping it.

This allows eliminating the T: [const] Destruct bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit drop_in_place::<Option<T>>() that will never do anything (and which might even persist after optimization).

@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @ibraheemdev

rustbot has assigned @ibraheemdev.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@kpreid

Copy link
Copy Markdown
ContributorAuthor

cc @cyb0124 (this change is based on their idea)

Comment threadlibrary/coretests/tests/option.rs Outdated
Comment threadlibrary/core/src/option.rs Outdated
@kpreid
kpreidforce-pushed the get-init-drop branch 2 times, most recently from ecc05f4 to 2e71187CompareNovember 6, 2025 23:31

@hkBsthkBst left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Looks good to me.

View changes since this review

Comment threadlibrary/core/src/option.rs Outdated
…ing it.
This allows eliminating the `T: [const] Destruct` bounds and avoids
generating an implicit `drop_in_place::<Option<T>>()` that will never do
anything.
Ideally, the compiler would prove that that drop is not necessary
itself, but it currently doesn't, even with `const_precise_live_drops`
enabled.
@ibraheemdev

Copy link
Copy Markdown
Member

The implementation looks good to me. r? libs-api for the unstable API change.

@rustbotrustbot added the T-libs-api [DEPRECATED; DO NOT USE] label Feb 9, 2026
@rustbotrustbot assigned the8472 and unassigned ibraheemdevFeb 9, 2026
@kpreid

kpreid commented Mar 9, 2026

Copy link
Copy Markdown
ContributorAuthor

Per advice:

@rustbot label -S-waiting-on-review +S-waiting-on-t-libs-api

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: S-waiting-on-libs-api

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@rustbotrustbot added S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 9, 2026
@oli-obk

Copy link
Copy Markdown
Contributor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

Also wondering about this pattern in general. Seems like sth const precise live drops could also handle, haven't looked at that in forever so I don't remember the details of it.

Anyway, if the final runtime MIR looks good, let's merge this

@kpreid

Copy link
Copy Markdown
ContributorAuthor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

I’m not familiar with how to do that, but I will look into it.

Seems like sth const precise live drops could also handle,

See prior discussion #148562 (comment) — in brief, having const_precise_live_drops would mean we are having the compiler doing static checking on how control flow affects values (whether the option is None), which is something that we generally only do for lint (e.g. if false {} is not counted as unreachable code).

@kpreid

Copy link
Copy Markdown
ContributorAuthor

oli-obk and I have looked at the MIR through dropping both implementations into Compiler Explorer and it seems generally similar, but also not very optimized either before or after.

@rustbot label +const-hack

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: const-hack

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@oli-obk

Copy link
Copy Markdown
Contributor

@bors r+ rollup

r? @oli-obk

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

📋 This PR cannot be approved because it currently has the following label: S-waiting-on-t-libs-api.

@rustbotrustbot assigned oli-obk and unassigned the8472Mar 9, 2026
@ChrisDentonChrisDenton removed the S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] label Mar 9, 2026
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per rust-lang#148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@matthiaskrgr

Copy link
Copy Markdown
Member

@bors yield

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153628.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
Rollup of 8 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #149931 (rustdoc: don't give depreciation notes special handling)
- #153608 (ast_passes: unsupported arch w/ scalable vectors)
- #153609 (Add missing `Diag::with_span_suggestion_with_style` method)
- #153610 (Only lint unused features if they are unstable)
- #153616 (Update `sysinfo` version to `0.38.4`)
- #153619 (Update books)
- #153624 (Ping fmease on parser modifications)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@Zalathar

Copy link
Copy Markdown
Member

The dist-x86_64-linux job is stuck.

@bors yield

@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153631.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@rust-borsrust-borsBot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 10, 2026
@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 8744ff0 failed: CI. Failed job:

@Zalathar

Copy link
Copy Markdown
Member

@bors retry (network failure)

@rust-borsrust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 10, 2026
rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

A job failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)
/dev/sda15 105M 6.2M 99M 6% /boot/efi
tmpfs 1.6G 12K 1.6G 1% /run/user/1001
================================================================================
Sufficient disk space available (95001912KB >= 52428800KB). Skipping cleanup.
##[group]Run src/ci/scripts/setup-environment.sh
src/ci/scripts/setup-environment.sh
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors
rust-borsBot merged commit ce97229 into rust-lang:mainMar 10, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 10, 2026
rust-timer added a commit that referenced this pull request Mar 10, 2026
Rollup merge of #148562 - kpreid:get-init-drop, r=oli-obk
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@kpreid
kpreid deleted the get-init-drop branch March 10, 2026 20:40
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
Rollup of 4 pull requests
Successful merges:
- rust-lang/rust#148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- rust-lang/rust#153325 (tests/ui/cfg: add annotations for reference rules)
- rust-lang/rust#153621 (Remove `TyCtxt::node_span_lint` method)
- rust-lang/rust#153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-libsRelevant to the library team, which will review and decide on the PR/issue.T-libs-api[DEPRECATED; DO NOT USE]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@kpreid@rustbot@ibraheemdev@oli-obk@ChrisDenton@matthiaskrgr@Zalathar@rust-log-analyzer@clarfonthey@hkBst@the8472
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

In Option::get_or_insert_with(), forget the None instead of dropping it. - #148562

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop
Mar 10, 2026
Merged

In Option::get_or_insert_with(), forget the None instead of dropping it.#148562
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
kpreid:get-init-drop

Conversation

@kpreid

@kpreidkpreid commented Nov 6, 2025

Copy link
Copy Markdown
Contributor

View all comments

Per #148486 (comment)

In Option::get_or_insert_with(), after replacing the None with Some, forget the None instead of dropping it.

This allows eliminating the T: [const] Destruct bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit drop_in_place::<Option<T>>() that will never do anything (and which might even persist after optimization).

@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Nov 6, 2025
@rustbot

Copy link
Copy Markdown
Collaborator

r? @ibraheemdev

rustbot has assigned @ibraheemdev.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@kpreid

Copy link
Copy Markdown
ContributorAuthor

cc @cyb0124 (this change is based on their idea)

Comment threadlibrary/coretests/tests/option.rs Outdated
Comment threadlibrary/core/src/option.rs Outdated
@kpreid
kpreidforce-pushed the get-init-drop branch 2 times, most recently from ecc05f4 to 2e71187CompareNovember 6, 2025 23:31

@hkBsthkBst left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Looks good to me.

View changes since this review

Comment threadlibrary/core/src/option.rs Outdated
…ing it.
This allows eliminating the `T: [const] Destruct` bounds and avoids
generating an implicit `drop_in_place::<Option<T>>()` that will never do
anything.
Ideally, the compiler would prove that that drop is not necessary
itself, but it currently doesn't, even with `const_precise_live_drops`
enabled.
@ibraheemdev

Copy link
Copy Markdown
Member

The implementation looks good to me. r? libs-api for the unstable API change.

@rustbotrustbot added the T-libs-api [DEPRECATED; DO NOT USE] label Feb 9, 2026
@rustbotrustbot assigned the8472 and unassigned ibraheemdevFeb 9, 2026
@kpreid

kpreid commented Mar 9, 2026

Copy link
Copy Markdown
ContributorAuthor

Per advice:

@rustbot label -S-waiting-on-review +S-waiting-on-t-libs-api

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: S-waiting-on-libs-api

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@rustbotrustbot added S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 9, 2026
@oli-obk

Copy link
Copy Markdown
Contributor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

Also wondering about this pattern in general. Seems like sth const precise live drops could also handle, haven't looked at that in forever so I don't remember the details of it.

Anyway, if the final runtime MIR looks good, let's merge this

@kpreid

Copy link
Copy Markdown
ContributorAuthor

Can you check the final optimized runtime MIR before and after your change? I'm not sure we're optimizing the new code properly.

I’m not familiar with how to do that, but I will look into it.

Seems like sth const precise live drops could also handle,

See prior discussion #148562 (comment) — in brief, having const_precise_live_drops would mean we are having the compiler doing static checking on how control flow affects values (whether the option is None), which is something that we generally only do for lint (e.g. if false {} is not counted as unreachable code).

@kpreid

Copy link
Copy Markdown
ContributorAuthor

oli-obk and I have looked at the MIR through dropping both implementations into Compiler Explorer and it seems generally similar, but also not very optimized either before or after.

@rustbot label +const-hack

@rustbot

Copy link
Copy Markdown
Collaborator

Error: Unknown labels: const-hack

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

@oli-obk

Copy link
Copy Markdown
Contributor

@bors r+ rollup

r? @oli-obk

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

📋 This PR cannot be approved because it currently has the following label: S-waiting-on-t-libs-api.

@rustbotrustbot assigned oli-obk and unassigned the8472Mar 9, 2026
@ChrisDentonChrisDenton removed the S-waiting-on-t-libs-api [DEPRECATED; DO NOT USE] label Mar 9, 2026
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per rust-lang#148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@matthiaskrgr

Copy link
Copy Markdown
Member

@bors yield

@rust-bors

rust-borsBot commented Mar 9, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153628.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
Rollup of 8 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #149931 (rustdoc: don't give depreciation notes special handling)
- #153608 (ast_passes: unsupported arch w/ scalable vectors)
- #153609 (Add missing `Diag::with_span_suggestion_with_style` method)
- #153610 (Only lint unused features if they are unstable)
- #153616 (Update `sysinfo` version to `0.38.4`)
- #153619 (Update books)
- #153624 (Ping fmease on parser modifications)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 9, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@Zalathar

Copy link
Copy Markdown
Member

The dist-x86_64-linux job is stuck.

@bors yield

@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #153631.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors

This comment has been minimized.

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@rust-borsrust-borsBot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 10, 2026
@rust-bors

rust-borsBot commented Mar 10, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 8744ff0 failed: CI. Failed job:

@Zalathar

Copy link
Copy Markdown
Member

@bors retry (network failure)

@rust-borsrust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 10, 2026
rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

A job failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)
/dev/sda15 105M 6.2M 99M 6% /boot/efi
tmpfs 1.6G 12K 1.6G 1% /run/user/1001
================================================================================
Sufficient disk space available (95001912KB >= 52428800KB). Skipping cleanup.
##[group]Run src/ci/scripts/setup-environment.sh
src/ci/scripts/setup-environment.sh
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

rust-borsBot pushed a commit that referenced this pull request Mar 10, 2026
Rollup of 4 pull requests
Successful merges:
- #148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- #153325 (tests/ui/cfg: add annotations for reference rules)
- #153621 (Remove `TyCtxt::node_span_lint` method)
- #153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
@rust-bors
rust-borsBot merged commit ce97229 into rust-lang:mainMar 10, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 10, 2026
rust-timer added a commit that referenced this pull request Mar 10, 2026
Rollup merge of #148562 - kpreid:get-init-drop, r=oli-obk
In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.
Per #148486 (comment)
In `Option::get_or_insert_with()`, after replacing the `None` with `Some`, forget the `None` instead of dropping it.
This allows eliminating the `T: [const] Destruct` bounds, making the functions more flexible in (unstable) const contexts, and avoids generating an implicit `drop_in_place::<Option<T>>()` that will never do anything (and which might even persist after optimization).
@kpreid
kpreid deleted the get-init-drop branch March 10, 2026 20:40
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
Rollup of 4 pull requests
Successful merges:
- rust-lang/rust#148562 (In `Option::get_or_insert_with()`, forget the `None` instead of dropping it.)
- rust-lang/rust#153325 (tests/ui/cfg: add annotations for reference rules)
- rust-lang/rust#153621 (Remove `TyCtxt::node_span_lint` method)
- rust-lang/rust#153627 (rustdoc-json: Improve docs for `ItemEnum::item_kind`)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-libsRelevant to the library team, which will review and decide on the PR/issue.T-libs-api[DEPRECATED; DO NOT USE]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

11 participants

@kpreid@rustbot@ibraheemdev@oli-obk@ChrisDenton@matthiaskrgr@Zalathar@rust-log-analyzer@clarfonthey@hkBst@the8472