-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Require inherent impls to be located adjacent to their types #17059
Labels
A-resolve
Area: Path resolution
B-RFC-approved
Blocker: Approved by a merged RFC but not yet implemented.
Milestone
Comments
pcwalton
added
I-nominated
B-RFC-approved
Blocker: Approved by a merged RFC but not yet implemented.
A-resolve
Area: Path resolution
labels
Sep 7, 2014
1.0, P-backcompat-lang. |
lnicola
pushed a commit
to lnicola/rust
that referenced
this issue
Apr 20, 2024
…r=Veykril internal: make function builder create ast directly I am working on rust-lang#17050. In the process, I noticed a place in the code that could be refactored. Currently, the `function builder` creates the `ast` through the `function template` , but those two processes can be combined into one function. I thought I should work on this first and created a PR.
lnicola
pushed a commit
to lnicola/rust
that referenced
this issue
Apr 20, 2024
…r=Veykril internal: make function builder create ast directly I am working on rust-lang#17050. In the process, I noticed a place in the code that could be refactored. Currently, the `function builder` creates the `ast` through the `function template` , but those two processes can be combined into one function. I thought I should work on this first and created a PR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-resolve
Area: Path resolution
B-RFC-approved
Blocker: Approved by a merged RFC but not yet implemented.
RFC: rust-lang/rfcs#155
Nominating for 1.0, P-backcompat-lang.
The text was updated successfully, but these errors were encountered: