-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
Update tracking issue for PinCoerceUnsized #150113
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
Conversation
This comment has been minimized.
This comment has been minimized.
545df8f to
78f52c1
Compare
|
Hmm, so should the impls be unstable under the same feature? It's super weird because
I'm going to go ahead and say yes, since it just doesn't actually matter in practice Thanks :) @bors r+ rollup |
|
Yeah I don't know 🤷♀️ |
…112, r=jackh726 Update tracking issue for PinCoerceUnsized This uses the newly created tracking issue rust-lang#150112. Please see rust-lang#68015 (comment) for motivation. r? `@jackh726`
if you do want to make them actually unstable we have the ability to mark impls as unstable. But given these impls are actually usable on stable that would probably not work |
…uwer Rollup of 4 pull requests Successful merges: - #149922 (Tidying up tests/ui/issues 14 tests [5/N]) - #150095 (Port `#[rustc_no_implicit_autorefs]`, `#[rustc_lint_opt_ty]`, and `#[rustc_lint_query_instability]` attributes to be parsed) - #150099 ([rustdoc] Fix invalid handling of field followed by negated macro call) - #150113 (Update tracking issue for PinCoerceUnsized) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of #150113 - Darksonn:pin-coerce-unsized-to-150112, r=jackh726 Update tracking issue for PinCoerceUnsized This uses the newly created tracking issue #150112. Please see #68015 (comment) for motivation. r? ``@jackh726``
This uses the newly created tracking issue #150112.
Please see #68015 (comment) for motivation.
r? @jackh726