-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Closed
Labels
B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.Blocker: Approved by a merged RFC but not yet implemented.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCE-help-wantedCall for participation: Help is requested to fix this issue.Call for participation: Help is requested to fix this issue.E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.S-tracking-design-concernsStatus: There are blocking design concerns.Status: There are blocking design concerns.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.T-langRelevant to the language teamRelevant to the language teamT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Description
This is a tracking issue for the RFC "?
in main
" (rust-lang/rfcs#1937).
Steps:
- Implement the RFC (mentoring instructions can be found here).
-
?
inmain
(Implements RFC 1937:?
inmain
#46479) -
?
in doctest -
?
in#[test]
-
- Adjust documentation (see instructions on forge)
- Stabilization PR (see instructions on forge)
Stabilizations:
- Stabilize
main
with non-() return types (Stabilizemain
with non-() return types #48453) Merged in Stabilize termination_trait, split out termination_trait_test #49162 - Stabilize unit tests with non-() return types (Stabilize unit tests with non-
()
return type #48854)
Related issues:
- Error message for unit tests is not great (error message when unit test type does not implement
Termination
is ungreat #50291)
Unresolved questions:
- The name of the trait being introduced
- The precise initial implementations
- this will be stabilized by Stabilize
main
with non-() return types #48453
- this will be stabilized by Stabilize
- exit codes (discussion) Moved to a separate tracking issue, Tracking issue for std::process::ExitCode (feature process_exitcode_placeholder) #48711
this will be stabilized by Stabilizeno longer true after Restrict the Termination impls to simplify stabilization #48497main
with non-() return types #48453
Timmmm, xTibor, killercup, m0n0chr0m3, joe-askattest and 10 morejonhoo, durka, steveklabnik, BookOwl, niklasf and 16 moreschneiderfelipeschneiderfelipe
Metadata
Metadata
Assignees
Labels
B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.Blocker: Approved by a merged RFC but not yet implemented.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCE-help-wantedCall for participation: Help is requested to fix this issue.Call for participation: Help is requested to fix this issue.E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.S-tracking-design-concernsStatus: There are blocking design concerns.Status: There are blocking design concerns.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.T-langRelevant to the language teamRelevant to the language teamT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.