-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Refactor how the parser looks for sub-modules #26750
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 makes the functionality usable from outside the parser
r? @sfackler (rust_highfive has picked a reviewer for you, use r? to override) |
/// Information about the path to a module. | ||
pub struct ModulePath { | ||
pub name: String, | ||
pub path_exists: bool, |
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 probably makes more sense inside of ModulePathError
, right?
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.
It's needed in both cases. In the non-error case, there can still be an error if !self.owns_directory
and then we need to check path_exists
. That can't be checked without a parser, so we need to be pass out path_exists
here.
@sfackler review ping |
@bors r+ sorry |
📌 Commit f3ba950 has been approved by |
This makes the functionality usable from outside the parser
This makes the functionality usable from outside the parser