You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The meeting is about the direction that rust#128045 should take and how they could be implemented.
The proposal was opened by @pnkfelix who then handed development to @celinval. It was discussed briefly in a compiler triage meeting. This works intersect with the attribute refactoring, which is tracked rust#131229.
The design meeting should focus on validating/refining the design of rust#128045 and how it fits in a bigger attribute refactoring story.
About this issue
This issue corresponds to a meeting proposal for the compiler team steering meeting. It corresponds to a possible topic of
discussion. You can read more about the steering meeting procedure
here.
Comment policy
These issues are meant to be used as an "announcements channel"
regarding the proposal, and not as a place to discuss the technical
details. Feel free to subscribe to updates. We'll post comments when
reviewing the proposal in meetings or making a scheduling decision.
In the meantime, if you have questions or ideas, ping the proposers
on Zulip (or elsewhere).
The text was updated successfully, but these errors were encountered:
Meeting proposal info
Summary
The meeting is about the direction that rust#128045 should take and how they could be implemented.
The proposal was opened by @pnkfelix who then handed development to @celinval. It was discussed briefly in a compiler triage meeting. This works intersect with the attribute refactoring, which is tracked rust#131229.
The design meeting should focus on validating/refining the design of rust#128045 and how it fits in a bigger attribute refactoring story.
About this issue
This issue corresponds to a meeting proposal for the compiler team
steering meeting. It corresponds to a possible topic of
discussion. You can read more about the steering meeting procedure
here.
Comment policy
These issues are meant to be used as an "announcements channel"
regarding the proposal, and not as a place to discuss the technical
details. Feel free to subscribe to updates. We'll post comments when
reviewing the proposal in meetings or making a scheduling decision.
In the meantime, if you have questions or ideas, ping the proposers
on Zulip (or elsewhere).
The text was updated successfully, but these errors were encountered: