Beginner-level Rustc Issues To Work On

[fiery hatch]

(bump)

[verbal geyser]

[PR is already sent]

[fiery hatch]

https://github.com/rust-lang/rust/issues/96928 (a pr was made already but was closed as inactive)

[silver sedge]

thanks for linking - the issue was out of date, updated it

https://github.com/rust-lang/rust/issues/90672 is another good first issue

[fiery hatch]

https://github.com/rust-lang/rust/issues/98861 - easy doc issue on the Write trait

[woven tusk]

there's already a PR out for that one (but I noticed a problem and left a comment about it, so thanks for the link)

[fiery hatch]

ah right i didnt see that

if someone fancies writing tests for rustdoc: https://github.com/rust-lang/rust/issues/91113

[fiery hatch]

Help with diagnostic translation: https://github.com/rust-lang/rust/issues/100717

[fiery hatch]

https://github.com/rust-lang/rust/issues/83518

[fiery hatch]

https://github.com/rust-lang/rust/issues/90698

[silver sedge]

oh heh I forgot about that one

[fiery hatch]

yeh i just cleared the person who self-assigned and didnt get to work on it 😄

[fiery hatch]

https://github.com/rust-lang/rust/issues/76547

[fiery hatch]

https://github.com/rust-lang/rust/issues/42849

[verbal geyser]

<@&631915156854538260>

[warm helm]

@fiery hatch I found that most of the issues got claimed already 😦

[normal talon]

https://github.com/rust-lang/rust/issues/105168

I'm not sure whether the existing instructions are enough for a beginner but you can ask me if you need more help

[fiery hatch]

yeah but you can re-claim an issue, if someone claimed it a month ago and hasn't worked on it or indicated that they done any work on it

[verbal geyser]

Are there more beginner friendly issues open? 🙂

[fiery hatch]

you can look for E-easy ones that aren't claimed or claimed a while back (at least 2 weeks) with no progress at all being made and reclaim those

[fiery hatch]

https://github.com/rust-lang/rust/issues/105107

[normal talon]

https://github.com/rust-lang/rust/issues/107370

a trivial issue, great for getting familiar with building and running the compiler and the contribution process

just comment @rustbot claim

I guess the slightly tricky thing here is adding a test

nevermind, fixed already

[normal talon]

https://github.com/rust-lang/rust/issues/96606

this shouldn't be too hard

[silver sedge]

https://github.com/rust-lang/rust/issues/108051

[fiery hatch]

this requires a testcase to be added: https://github.com/rust-lang/rust/issues/56098

[silver sedge]

https://github.com/rust-lang/rust/issues/109502 might be fun

[fiery hatch]

https://github.com/rust-lang/rust/issues/40713

[tropic mountain]

This doesn’t look very beginner to me

[silver sedge]

it's beginner in that it doesn't need a lot of context about how the compiler or language work, but yes, it's a non-trivial amount of work

[silver sedge]

ditto https://github.com/rust-lang/rust/issues/109859

[silver sedge]

evergreen list of how to get started: https://rustc-dev-guide.rust-lang.org/#what-should-i-work-on

[tulip garnet]

Many API are now in const https://github.com/rust-lang/rust/blob/master/RELEASES.md#stabilized-apis.
I am having hard time finding the related PR. Is it doable for beginners to port other API to const?

[fiery hatch]

doc issue https://github.com/rust-lang/rust/issues/83999

[lilac mango]

This one is closed now

does @rustbot claim mean someone has taken ownership of the issue @fiery hatch ?

oh rustbot unassigned it from someone. huh

[fiery hatch]

yes it does, but it we unassign it if there is no activity after a few weeks

[fiery hatch]

https://github.com/rust-lang/rust/issues/111839

[modest brook]

I made some progress on this. Look at the linked PRs.

[fiery hatch]

https://github.com/rust-lang/rust/issues/113135

[silver sedge]

https://github.com/rust-lang/rustc-dev-guide/issues/1707

[fiery hatch]

This issue is available again: https://github.com/rust-lang/rust/issues/105225. Most of the work is done here: https://github.com/rust-lang/rust/pull/105635 so it just needs to be redone with concerns addressed

[tropic mountain]

I may try this later. Not sure if its a meaningful first contrib but it will certainly be a contrib

[fiery hatch]

all contributions are meaningful

[tropic mountain]

its just a testcase

Lemme finish the part of my essay I'm working on and then head into linsus

[fiery hatch]

sure take your time no worries 🙂

[tropic mountain]

I'll be doing it this weekend™️

[fiery hatch]

thanks

please do a @rustbot claim on the issue so nobody else works on it

[charred frigate]

Hey! I'm new around here, not sure how this works. Are new issues updated in this thread? Are there any beginner-friendly issues that need help rn?

[tropic mountain]

no going back

I'll start at 6 ig

[fiery hatch]

take your time, no worries

[regal night]

Where to find open issues ?

[fiery hatch]

on the issue tracker look for issues that are marked e-easy/e-mentor which are not claimed

[fiery hatch]

~~https://github.com/rust-lang/rust/issues/116064~~ [claimed by someone atm]

[normal talon]

https://github.com/rust-lang/rust/issues/116121

[tropic mountain]

I literally lost all time to do this

uh

how 2 unclaim

[eternal steppe]

@rustbot release-assignment IIRC
https://rustc-dev-guide.rust-lang.org/rustbot.html#issue-claiming

hi nils

[normal talon]

hi

i always think its @rustbot release

well, these days i have no use for it as i dont need rustbot anymore

[normal talon]

i unassigned you since seem to have forgotten

[jade forge]

I would love to do this how would i proceed is there a work flow?

[normal talon]

write @rustbot claim
and then look at the contributing docs linked in the readme

[jade forge]

@rustbot claim

Where would I use that command at? @normal talon

[normal talon]

on the issue

[jade forge]

Oh on github ?

[normal talon]

yes

[normal talon]

this has a PR already

[fiery hatch]

oh uhm

[fiery hatch]

https://github.com/rust-lang/rust/issues/110163 (mentoring notes present in the issue as well)

[tropic mountain]

I guess this is dead?

[fiery hatch]

Haven't looked for issues. If I find one will post it here

[ebon citrus]

Beginner issues tend to be snapped up quite quickly. Also I guess rustc has less low hanging fruit than it used to.

[pine rapids]

me omw to introduce bad code in rustc to give beginners easy things to do

[vale tulip]

broken windows help the economy

[fiery hatch]

A docs issue where you need to dig up the time complexity and add it to each method: [bonus if you do it for other collections where they aren't mentioned] https://github.com/rust-lang/rust/issues/100182

[barren wren]

LET'S GO

i can do it

[fiery hatch]

you can claim the issue if you wish

ah shit someone claimed it already

[void briar]

see if guy does it

[spice hinge]

Do you know if there are any guidelines for which methods need time complexity headings? For example, does it make sense to annotate something more trivial like len being O(1)?

[normal talon]

there are none

I'd only add it to places where it's notable

[fiery hatch]

https://github.com/rust-lang/rust/issues/121502 (cc @gritty drift )

[tropic mountain]

Ok I might have time today for this pretty simple change

My first contribution to rustc will be uh pretty minimal

[void briar]

ought to claim it

[void briar]

is this just changing a string?

i dont really see anything wrong with the current warning

[tropic mountain]

yes

[gritty drift]

https://github.com/rust-lang/rust/issues/121876
We'd like to port all the run-make tests to use Rust instead of Makefiles. Some of the tests are easier to port than others. You might be able to find some of the easier tests to port.

[normal talon]

[fiery hatch]

an old e-easy issue that's still open: https://github.com/rust-lang/rust/issues/68962

[fickle harbor]

Hey @fiery hatch
I'm new to rust, and learning it.
If possible can you describe what's the issue here, I want to contribute on it.

While returning from fn,
r#fina should be r#final ?

[fiery hatch]

yes

[fickle harbor]

@fiery hatch
I didn't understand, to which question you said yes.
Can you describe the issue here.
I didn't get it.

[fiery hatch]

lol

my bad

[fiery hatch]

yes you got this right. i would also recommend asking on zulip since it's either to help there than here as this is mainly a list of issues

[fickle harbor]

Sure, thank you

[indigo kite]

this is std, not rustc, but sometimes please add NonNull::<[T]>::is_empty: https://github.com/rust-lang/rust/issues/71146#issuecomment-2008373983

[void briar]

because of clippy?

[fiery hatch]

(note that this will need an ACP)

[dark pagoda]

hello, hello, the press gang is here: https://github.com/rust-lang/rust/issues/122899

[dark pagoda]

to clarify the debuglink test is definitely not beginner-level for any reasonable definition of "beginner", the others are notably less... weird.

[fiery hatch]

An easy documentation fix: https://github.com/rust-lang/rust/issues/124882

[void briar]

lmao i looked at this issue history and its hilarious

claim fixed
doesnt pr
claim
doesnt pr
claim
unclaimed
reclaimed
no pr
somebody finally fixes it

[fiery hatch]

yah 😄

[fiery hatch]

that's sadly true for many issues that are still open

[void briar]

guy did it

[indigo kite]

DynMetadata::size_of has a comment that it returns the size of the dyn Trait part only, for things like (u32, dyn Send). This should probably be clearly stated in the documentation (and in documentation of other similar functions, DynMetadata::{align_of,layout}).

So if someone is looking to make a quick doc fix =)

[fiery hatch]

An easy one line change: https://github.com/rust-lang/rust/issues/102743 just need to change a line in https://doc.rust-lang.org/rustc/lints/index.html

[elder moon]

I've submitted a PR (my first rust PR) at https://github.com/rust-lang/rust/pull/127504 thanks!

[fiery hatch]

thanks 🙂

[fiery hatch]

an old issue which just requires a test to be added: https://github.com/rust-lang/rust/issues/89220

[indigo kite]

https://github.com/rust-lang/rust/pull/110555 already contains tests, so I'm not sure it's necessary?

[fiery hatch]

uhm then it's the case of the tracking issue not being updated 😄

[indigo kite]

which tracking issue? you mean 89220? can't we just close it?

[fiery hatch]

yes i'm closing it right now

i did see the comment earlier but it hought maybe more tests were expected so didn't check further 😄

[indigo kite]

thanks!

[fiery hatch]

~~ this issue just requires a test added https://github.com/rust-lang/rust/issues/51525~~ closed

[fiery hatch]

https://github.com/rust-lang/rust/issues/116652

[fiery hatch]

Here's a very trivial pr opportunity: https://github.com/rust-lang/rust/issues/110144

[dusk ledge]

nice

i would

but i'm too lazy

[fiery hatch]

it's a one line fix lol

Beginner-level rustc issues that people can work on.
If you want to work on any of them, you can comment with @rustbot claim on the issue itself
Guide to working with rustc: https://rustc-dev-guide.rust-lang.org/contributing.html

if you have any doubts or need help while working on your prs you can ask your questions here, in the other channels or on zulip.

Doc issue to fix select_nth: https://github.com/rust-lang/rust/issues/97982

[fiery hatch]

~~Another simple doc fix: https://github.com/rust-lang/rust/issues/97981~~ FIXED

[turbid grotto]

that one has a pr now

[fiery hatch]

~~If someone loves writing documentation: https://github.com/rust-lang/rust/issues/80437#issuecomment-1150255531~~

[fiery hatch]

Some error codes still require a long description. You can pick one error code that's not checked and not an internal one and submit a pr for it : https://github.com/rust-lang/rust/issues/61137

[wild trellis]

https://github.com/rust-lang/rust/issues/98379

[fiery hatch]

https://github.com/rust-lang/rust/issues/98797

[fiery hatch]

easy issue: https://github.com/rust-lang/rust/issues/99144