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

Tracking Issue for x suggest #109933

Open
2 of 4 tasks
Ezrashaw opened this issue Apr 4, 2023 · 10 comments
Open
2 of 4 tasks

Tracking Issue for x suggest #109933

Ezrashaw opened this issue Apr 4, 2023 · 10 comments
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC E-needs-design This issue needs exploration and design to see how and if we can fix/implement it T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.

Comments

@Ezrashaw
Copy link
Contributor

Ezrashaw commented Apr 4, 2023

Tracking issue for x suggest subcommand and implementation of recommendations. Note that this isn't a traditional tracking issue for a feature but just a place to keep track of implementation.

See the zulip stream and the initial issue for more information and rationale about this change.

cc @albertlarsan68 @jyn514

@Ezrashaw
Copy link
Contributor Author

Ezrashaw commented Apr 4, 2023

@rustbot label +E-easy +E-mentor +E-help-wanted +T-bootstrap

@rustbot rustbot added E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. E-help-wanted Call for participation: Help is requested to fix this issue. E-mentor Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) labels Apr 4, 2023
@albertlarsan68
Copy link
Member

I think @rust-lang/libs @rust-lang/compiler should participate.
@rustbot label +T-libs +T-compiler

@rustbot rustbot added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Apr 4, 2023
@DavidCoy77
Copy link

Hi! I'd love to get started contributing to Rust, but I'd need a little help getting started since this would be my first ever GitHub contribution. You've included the tags Easy, Help-Wanted, and Mentor, so if you're willing to help, I'm eager to get to work. Thanks!

@onur-ozkan
Copy link
Member

I don't have the time for mentoring these days(moving my apartment).

@DavidCoy77
Copy link

No problem @onur-ozkan

@Dylan-DPC
Copy link
Member

@DavidCoy77 if you are still interested in this, you can claim the issue by commenting with @rustbot claim and then ask for help on zulip

@albertlarsan68
Copy link
Member

@DavidCoy77, if you still are looking for mentorship on this issue, DM me on Zulip, and we can talk about it.

@hrkskov
Copy link

hrkskov commented Jan 18, 2024

Hi. I'm also interested in this issue as the first time for contribution to rust!

@DavidCoy77
Can I work on this?

@ismailarilik
Copy link
Contributor

Image

Do we want this? =)
And if we want, what should it check?

@Ezrashaw
Copy link
Contributor Author

Ezrashaw commented Oct 4, 2024

Do we want this? =) And if we want, what should it check?

Thanks for the interest! When I wrote the "static suggestions" code, I was vaguely thinking that there could be issues with this code turning into spaghetti and not being formatted correctly (with macros and all). So I thought that a tidy lint could enforce a common style or such like.

static_suggestions! {
["*.md"] => [
sug!("test", 0, ["linkchecker"]),
],
["compiler/*"] => [
sug!("check"),
sug!("test", 1, ["tests/ui", "tests/run-make"]),
],
["compiler/rustc_mir_transform/*"] => [
sug!("test", 1, ["mir-opt"]),
],
[
"compiler/rustc_mir_transform/src/coverage/*",
"compiler/rustc_codegen_llvm/src/coverageinfo/*",
] => [
sug!("test", 1, ["coverage"]),
],
["src/librustdoc/*"] => [
sug!("test", 1, ["rustdoc"]),
],
}

That hasn't happened yet, since there aren't that many suggestions, so there's probably not too much point doing work on this until there are more, and a better defined format for defining suggestions is implemented (like in a separate text file?)

I think that the most useful thing with this tool is to increase its coverage, but I'd definitely be happy if you wanted to write some sort of tidy lint for it.

@jieyouxu jieyouxu added E-needs-design This issue needs exploration and design to see how and if we can fix/implement it C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC and removed E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. E-mentor Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion. E-help-wanted Call for participation: Help is requested to fix this issue. labels Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC E-needs-design This issue needs exploration and design to see how and if we can fix/implement it T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

9 participants