-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking Issue for constifying Result
methods that drop values
#92384
Comments
Turns out you actually can't make these const, at least for now. So, closing. |
Reopened now that I've found a proper way to do this. Linked the tracking issue for |
const_result_option
Result
methods that drop values
Add Result::{ok, err, and, or, unwrap_or} as const Already opened tracking issue rust-lang#92384. I don't think that this should actually cause any issues as long as the constness is unstable, but we may want to double-check that this doesn't get interpreted as a weird `Drop` bound even for non-const usages.
Add Result::{ok, err, and, or, unwrap_or} as const Already opened tracking issue rust-lang#92384. I don't think that this should actually cause any issues as long as the constness is unstable, but we may want to double-check that this doesn't get interpreted as a weird `Drop` bound even for non-const usages.
Add Result::{ok, err, and, or, unwrap_or} as const Already opened tracking issue rust-lang#92384. I don't think that this should actually cause any issues as long as the constness is unstable, but we may want to double-check that this doesn't get interpreted as a weird `Drop` bound even for non-const usages.
Add Result::{ok, err, and, or, unwrap_or} as const Already opened tracking issue rust-lang#92384. I don't think that this should actually cause any issues as long as the constness is unstable, but we may want to double-check that this doesn't get interpreted as a weird `Drop` bound even for non-const usages.
Duplicate of #82814? |
That appears to be a meta tracking issue, this is specifically for these methods. |
At least when I created it, it was not intended to be a meta issue. |
Yes, but for now, these methods point to this one, since they presumably would need their own FCP. |
I figured it would be a partial stabilization of #82814. Not a big deal either way, just wanted to bring it to your attention 🙂 |
This got removed by #110393. |
Feature gate:
#![feature(const_result_drop)]
Public API
This is a tracking issue for the
const_result_drop
feature, which includes constness for the following methods:Note that these depend on the semantics for
~const Drop
, which is (probably) tracked in #67792.Steps / History
Unresolved Questions
The text was updated successfully, but these errors were encountered: