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

Reorganize the directory structure of librustc and the driver #1447

Closed
brson opened this issue Jan 6, 2012 · 1 comment
Closed

Reorganize the directory structure of librustc and the driver #1447

brson opened this issue Jan 6, 2012 · 1 comment
Assignees
Labels
C-cleanup Category: PRs that clean code up or issues documenting cleanup. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Jan 6, 2012

The driver is now just a small stub that calls librustc, but the source still lives under comp. These two things should be separated. I suggest moving librustc to src/librustc and driver.rs to src/rustc-driver.

@ghost ghost assigned brson Apr 12, 2012
@catamorphism
Copy link
Contributor

This is done.

celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
…1447)

* Changed copyright check to the new standard PR 1422.

* Fixed debug print.

* Added doc comment.

* Changed to proper doc-comment

* reverted test cases

* Changed generator test cases to new format.

* Added check that above our license is empty or comments

* Fixed merge fail

* Escaped backslash.

* Allowed empty 2nd line pattern discussed in rust-lang#1422

* Test case for maybe empty lines above.

* Changed from list to generator.
Kobzol pushed a commit to Kobzol/rust that referenced this issue Dec 30, 2024
bors pushed a commit to rust-lang-ci/rust that referenced this issue Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-cleanup Category: PRs that clean code up or issues documenting cleanup. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

2 participants