-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Add #[track_caller] for some function in core::mem. #86664
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
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.
Makes sense to me. Feel free to r=me if this doesn't need a full t-libs-api member's review.
Thanks for the review! @bors r=JohnTitor |
📌 Commit b490dbdeb427d4c54984085cf18c7dfd87f1dd6f has been approved by |
⌛ Testing commit b490dbdeb427d4c54984085cf18c7dfd87f1dd6f with merge a3d54864adfb5b8d713f9546460c80f2eccaa0a3... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
These functions can panic for some types. This makes the panic point to the code that calls e.g. mem::uninitialized(), instead of inside the definition of mem::uninitialized.
b490dbd
to
3f6dc9a
Compare
Rebased and blessed the test output. @bors r=JohnTitor |
📌 Commit 3f6dc9a has been approved by |
⌛ Testing commit 3f6dc9a with merge 34e37bdbb491451aa684976d765796616b217443... |
💔 Test failed - checks-actions |
@bors retry |
☀️ Test successful - checks-actions |
These functions can panic for some types. This makes the panic point to the code that calls e.g. mem::uninitialized(), instead of inside the definition of mem::uninitialized.