Changing -O
to opt-level=3
#828
Labels
final-comment-period
The FCP has started, most (if not all) team members are in agreement
major-change
A proposal to make a major change to rustc
T-compiler
Add this label so rfcbot knows to poll the compiler team
Proposal
The
-O
flag has existed for over 14 years, predating opt-levels entirely. It is somewhat surprising that it means opt-level=2, especially as Cargo's release profile uses level 3.In C compilers,(Not sure this part is true)-O
usually means a non-maximum opt level as some optimizations can cause unsoundness; Rust doesn't have this limitation.I'd like to propose changing this shorthand flag to a more useful default.
Process
The main points of the Major Change Process are as follows:
@rustbot second
.-C flag
, then full team check-off is required.@rfcbot fcp merge
on either the MCP or the PR.You can read more about Major Change Proposals on forge.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.
The text was updated successfully, but these errors were encountered: