-
Notifications
You must be signed in to change notification settings - Fork 55
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
Officially recognize carry over of cargo script #294
base: main
Are you sure you want to change the base?
Conversation
This was approved for 2025h2 and I figured I wouldn't bother carrying it over since so little was left but what was left was the cross-team stuff and I should have called this out. So this is rectifying that.
Talked with @nikomatsakis about holding a small FCP from the relevant teams for this. |
I wouldn't bother with a full FCP, I think if we can get agreement from the team leads that suffices (that's the standard for the RFC, after all). cc @rust-lang/compiler @rust-lang/lang @rust-lang/spec -- @epage wanted to do a late addition to the goals for the remaining |
| Rust-analyzer implementation | @epage | | | ||
| Standard reviews | ![Team][] [compiler] | | | ||
| Lang-team champion | ![Team][] [lang] | | | ||
| Design meeting | ![Team][] [lang] | | |
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.
| Design meeting | ![Team][] [lang] | | |
I don't see that we left any open questions on the RFC. It'd surprise me if this needed a design meeting.
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.
I'll probably also be point for the spec team.
This was approved for 2025h2 and I figured I wouldn't bother carrying it over since so little was left but what was left was the cross-team stuff and I should have called this out.
So this is rectifying that.
Rendered