Skip to content

Error code list which need to be updated to new format #35233

Description

@GuillaumeGomez

View all comments

If you want to work on one (or more) of the issues, just comment on it to say you're taking it!

You can read @jonathandturner's post about how to make the fixes. If you have any questions, ask us here or on #rust-internals on irc.mozilla.org.

Also, if you finish an issue and it has a "Bonus" part that you're not able to complete, just go ahead and close the issue and open a new issue for just the Bonus part. That way, someone else can jump in and work on the bonus part. You can cc me on the new issue and we can add it to the list above.

Here is the list of error codes:

Bonuses:

Note: bonuses may require more work in the compiler and may require some exploration.

EDIT: Don't forget to say "Part of #35233." in your PR so we can see who did what in here. Also, add "r? @GuillaumeGomez" or "r? @jonathandturner" to set us as reviewer.

Activity

  1. added
    metabugIssues about issues themselves ("bugs about bugs")
    on Aug 3, 2016
  2. cramertj commented on Aug 3, 2016

    @cramertj
    Member

    I guess I'll go first! I'll take 1, 4, 5, and 9.
    Edit: Since there was so much interest, I gave these away. @Roybie has 1, @TheZoq2 has 4, @pythoneer has 5, and @devshep has 9. Thanks for contributing, folks!

  3. pcn commented on Aug 3, 2016

    @pcn
    Contributor

    I have no idea what I'm doing. I'll take 10, 17, 23 and 25.

  4. silenuss commented on Aug 3, 2016

    @silenuss
    Contributor

    I've also got no idea what I'm doing. I'll take 27, 29, 30, and 34. This should be fun.

  5. sophiajt commented on Aug 3, 2016

    @sophiajt
    Contributor

    For the "I have no idea what I'm doing" crowd - I'm working on a blog post that's going up soon (hopefully tomorrow!) It goes through all the steps of how to update the errors.

    Thanks for jumping on them :) Once the blog goes up, I'll reply here with the link.

  6. stephen-lazaro commented on Aug 3, 2016

    @stephen-lazaro
    Contributor

    I've never done this before. I'd like to grab 91, 92, and 93 if that'd be helpful!

  7. shri3k commented on Aug 3, 2016

    @shri3k
    Contributor

    I'll take 40 and 46 even though I don't know much about traits.

    Edit: Removing 49 & 50 so that others have chance to contribute as well.

  8. jaredwy commented on Aug 3, 2016

    @jaredwy

    I will take 61, 63 and 69.

  9. razielgn commented on Aug 3, 2016

    @razielgn
    Contributor

    Booking 71, 76 and 79. 😃

  10. nickmass commented on Aug 3, 2016

    @nickmass
    Contributor

    I will take 55, 57, and 60

  11. theypsilon commented on Aug 3, 2016

    @theypsilon
    Contributor

    I take 94 and 384 (I think there are no more available)

  12. lukehinds commented on Aug 3, 2016

    @lukehinds
    Contributor

    Might I suggest folks just take on one or two issues, that way others wanting to learn, will have a chance to get involved too.

  13. cramertj commented on Aug 3, 2016

    @cramertj
    Member

    @lukehinds Yeah, I didn't realize the precedent I was setting, nor how much interest there would be in the issue. If others who haven't contributed before would like to take any of the ones I said I would do (1, 4, 5, 9), they're welcome to it.

  14. TheZoq2 commented on Aug 3, 2016

    @TheZoq2
    Contributor

    I'll gladly take 4 then

  15. 572 remaining items

  16. sophiajt commented on Sep 26, 2016

    @sophiajt
    Contributor

    @Coder206 - yup, anyone can work on E0446. If you're working on it now, you might want to finish it up and send in the PR before someone gets to it first.

  17. sophiajt commented on Sep 26, 2016

    @sophiajt
    Contributor

    Bonuses! There are also new bonuses if you want to work on a bonus

  18. mikhail-m1 commented on Oct 4, 2016

    @mikhail-m1
    Contributor

    @jonathandturner Any free bonuses? I'd like to take one

  19. sophiajt commented on Oct 4, 2016

    @sophiajt
    Contributor

    Yes! to @mikhail-m1 and anyone interested, there are 5 bonuses on the bonus list that haven't been completed yet. Please feel free to grab one!

  20. mikhail-m1 commented on Oct 4, 2016

    @mikhail-m1
    Contributor

    @jonathandturner I'll take 'Doesn't live long enough'

  21. gavinb commented on Oct 5, 2016

    @gavinb
    Contributor

    @jonathandturner Next time you update the list, I've completed the "EXXXX - Field unknown" bonus with #36798. Having a look at the others now.

  22. sophiajt commented on Oct 6, 2016

    @sophiajt
    Contributor

    @gavinb - great! It's updated

  23. sophiajt commented on Nov 4, 2016

    @sophiajt
    Contributor

    Long time no see! I just added a really juicy task with some good bonus material. Niko has gone into great pains to list out the steps that need to go into this, and it's fixing a common pain point: seeing _ instead of the name of the type variable.

    You can see the steps here: #36554 (comment)

  24. mikhail-m1 commented on Nov 12, 2016

    @mikhail-m1
    Contributor

    I've almost done EXXXX - Fix temporary message and EXXXX - Doesn't live long enough, working on EXXXX - Better mutability

  25. bstrie commented on Mar 21, 2017

    @bstrie
    Contributor

    @jonathandturner Looks like all these are done except for the "bonus" bugs. Worth closing this issue?

  26. GuillaumeGomez commented on Mar 21, 2017

    @GuillaumeGomez
    MemberAuthor

    Make a smaller one would be nice. I'll close once the new smaller one has been created.

  27. estebank commented on Feb 27, 2018

    @estebank
    Contributor

    @GuillaumeGomez I feel like this ticket can now be closed, as every action item has been taken care of.

  28. Putaek84 commented on May 21, 2026

    @Putaek84
  29. rustbot commented on May 21, 2026

    @rustbot
    Collaborator

    Error: Parsing assign command in comment failed: specify user to assign to (if you want to reroll without a specific reviewer in mind, use @rustbot reroll) when parsing: laumeGomez[!]" or "r? @

    Parsing assign command in comment failed: specify user to assign to (if you want to reroll without a specific reviewer in mind, use @rustbot reroll) when parsing: handturner[!]" to set u

    Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

  30. rustbot commented on May 21, 2026

    @rustbot
    Collaborator

    Error: Parsing assign command in comment failed: specify user to assign to (if you want to reroll without a specific reviewer in mind, use @rustbot reroll) when parsing: @[!]

    Parsing

    Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-diagnosticsArea: Messages for errors, warnings, and lintsC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.metabugIssues about issues themselves ("bugs about bugs")

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions