Skip to content
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

Compile UI tests as libraries by default #842

Open
1 of 3 tasks
WaffleLapkin opened this issue Feb 23, 2025 · 1 comment
Open
1 of 3 tasks

Compile UI tests as libraries by default #842

WaffleLapkin opened this issue Feb 23, 2025 · 1 comment
Labels
major-change A proposal to make a major change to rustc T-compiler Add this label so rfcbot knows to poll the compiler team

Comments

@WaffleLapkin
Copy link
Member

Proposal

I propose to compile UI tests as libraries by default. I.e. compiletest will add --crate-type=lib by default, unless it's a run-pass/run-fail test (or other test type that requires a binary).

We could also add //@ crate-type [...] annotation to override this if need be.

The upside of compiling as libraries by default is that we will no longer need to workaround "missing main function" by adding fn main() {} in every test.

While it's not much, it's still useless noise that we also have to write every time.

Mentors or Reviewers

@jieyouxu would you like to review the compiletest changes?

For ui tests themselves literally anyone can review it, since it will just be fn main() {} deletion.

Process

The main points of the Major Change Process are as follows:

  • File an issue describing the proposal.
  • A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
    • Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
    • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
  • Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

@WaffleLapkin WaffleLapkin added major-change A proposal to make a major change to rustc T-compiler Add this label so rfcbot knows to poll the compiler team labels Feb 23, 2025
@rustbot
Copy link
Collaborator

rustbot commented Feb 23, 2025

Important

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.

Concerns or objections to the proposal should be discussed on Zulip and formally registered here by adding a comment with the following syntax:

@rfcbot concern reason-for-concern 
<description of the concern> 

Concerns can be lifted with:

@rfcbot resolve reason-for-concern 

See documentation at https://forge.rust-lang.org

cc @rust-lang/compiler

@rustbot rustbot added the to-announce Announce this issue on triage meeting label Feb 23, 2025
@apiraino apiraino removed the to-announce Announce this issue on triage meeting label Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
major-change A proposal to make a major change to rustc T-compiler Add this label so rfcbot knows to poll the compiler team
Projects
None yet
Development

No branches or pull requests

3 participants