-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
use_group_as RFC #1219
use_group_as RFC #1219
Conversation
👍 I don't see why we shouldn't make |
🐰 👍 + |
👍 including |
👍 |
Definitely want this, have been trying to use |
I think we should do this, and now seems like a reasonable time to re-open the issue. |
Updated to include |
Hear ye, hear ye. This RFC is entering final comment period. |
Awesome!! Let's do it. |
👍 |
|
||
# Motivation | ||
|
||
THe current design requires the above example to be written like this: |
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.
s/THe/The/
(unless it's intentional for some strange reason which I'm guessing it isn't)
👍 |
2 similar comments
👍 |
👍 |
I've definitely wanted this from time to time. 👍 from me. |
Definitely 👍, this seems like a reasonable inclusion, although I've never had need for the |
I have a working (but unpolished) implementation here (Needs grammar changes/tests and I should probably reorganize the ViewPath AST stuff too) |
It's official! The lang subteam has decided to accept this RFC. |
Tracking issue for this RFC is rust-lang/rust#27578 |
An implementation of [RFC 1219](rust-lang/rfcs#1219). The RFC is not merged yet, but once merged, this could be.
thank you! |
An implementation of [RFC 1219](rust-lang/rfcs#1219). The RFC is not merged yet, but once merged, this could be.
Allow aliasing imports when importing as a group.
Rendered
Postponed RFC #867 (See for previous discussion).
Closes #933