-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
WIP: PoC for derive(SmartPointer)
#123472
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @pnkfelix (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
Marking this as waiting-on-author since it's in draft mode @rustbot author |
☔ The latest upstream changes (presumably #123762) made this pull request unmergeable. Please resolve the merge conflicts. |
Tracking issue: rust-lang#123430
Rebased. @rustbot ready |
#[unstable(feature = "derive_smart_pointer", issue = "123430")] | ||
pub macro SmartPointer($item:item) { | ||
/* compiler built-in */ | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This macro definitely should not go into the root module of the core crate. Please look at other derive macros to see what the precedent is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rustbot author
A general comment: The tracking issue #123430 does not have any links to what this thing is supposed to do. I do not know how to evaluate this code without having an idea of what it is supposed to be used for. Is there someone from the T-lang team who has agreed to shepherd this experimental feature? or a link to perhaps a zulip topic or other linkable discussion thread that I could use to try to extract a rough idea of what this is for? |
I have a couple links in Rust for Linux's #2:
|
☔ The latest upstream changes (presumably #124424) made this pull request unmergeable. Please resolve the merge conflicts. |
@wedsonaf any updates on this? thanks |
Linking the RFC PR too: rust-lang/rfcs#3621. |
… r=davidtwco SmartPointer derive-macro <!-- If this PR is related to an unstable feature or an otherwise tracked effort, please link to the relevant tracking issue here. If you don't know of a related tracking issue or there are none, feel free to ignore this. This PR will get automatically assigned to a reviewer. In case you would like a specific user to review your work, you can assign it to them by using r? <reviewer name> --> Possibly replacing rust-lang#123472 for continued upkeep of the proposal rust-lang/rfcs#3621 and implementation of the tracking issue rust-lang#123430. cc `@Darksonn` `@wedsonaf`
Rollup merge of rust-lang#125575 - dingxiangfei2009:derive-smart-ptr, r=davidtwco SmartPointer derive-macro <!-- If this PR is related to an unstable feature or an otherwise tracked effort, please link to the relevant tracking issue here. If you don't know of a related tracking issue or there are none, feel free to ignore this. This PR will get automatically assigned to a reviewer. In case you would like a specific user to review your work, you can assign it to them by using r? <reviewer name> --> Possibly replacing rust-lang#123472 for continued upkeep of the proposal rust-lang/rfcs#3621 and implementation of the tracking issue rust-lang#123430. cc `@Darksonn` `@wedsonaf`
This should probably be closed as superseded by #125575. |
Tracking issue: #123430