-
Notifications
You must be signed in to change notification settings - Fork 13.3k
add test case for changing private methods #37124
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
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.
lgtm!
use point::Point; | ||
|
||
// FIXME(#37121) -- we should not need to typeck this again | ||
#[rustc_dirty(label="TypeckItemBody", cfg="rpass2")] |
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.
That fails too? Interesting.
} | ||
} | ||
|
||
/// A fn item that reads fields from `Point` but does not invoke methods |
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.
The comment should probably say "write" instead of "read".
@bors r+ rollup |
📌 Commit c560ca4 has been approved by |
…=michaelwoerister add test case for changing private methods The goal of this test case is to ensure we are getting the reuse we expect. This targets a particular change where we modify the body of a private inherent method defined on a struct, and looks at different ways we can use that struct. It checks for when type-checking would be needed as well as the actual reuse achieved. cc rust-lang#37121 r? @michaelwoerister
…=michaelwoerister add test case for changing private methods The goal of this test case is to ensure we are getting the reuse we expect. This targets a particular change where we modify the body of a private inherent method defined on a struct, and looks at different ways we can use that struct. It checks for when type-checking would be needed as well as the actual reuse achieved. cc rust-lang#37121 r? @michaelwoerister
The goal of this test case is to ensure we are getting the reuse we expect. This targets a particular change where we modify the body of a private inherent method defined on a struct, and looks at different ways we can use that struct.
It checks for when type-checking would be needed as well as the actual reuse achieved.
cc #37121
r? @michaelwoerister