Repository navigation
Error code list which need to be updated to new format #35233
Description
Activity
- addedmetabugIssues about issues themselves ("bugs about bugs")Issues about issues themselves ("bugs about bugs")
on Aug 3, 2016 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!I have no idea what I'm doing. I'll take 10, 17, 23 and 25.
Reacted by Taylor Cramer, Dustin Bensing and AdowrathI've also got no idea what I'm doing. I'll take 27, 29, 30, and 34. This should be fun.
Reacted by Taylor Cramer, Dustin Bensing, Isaac Goldberg and AdowrathFor 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.
Reacted by Taylor Cramer, Peter N, Peter Blackson, Andréy Lesnikóv, Frans Skarman, fxlae and AdowrathReacted by bstrie, silenuss, Peter N, Yojan Shrestha, Stephen Lazaro, Federico Ravasio, Dustin Bensing, Ember, Jakub Hlusička and AdowrathI've never done this before. I'd like to grab 91, 92, and 93 if that'd be helpful!
Reacted by Taylor Cramer, Dustin Bensing, Peter Delevoryas and AdowrathI'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.
Reacted by Taylor Cramer and Dustin BensingI will take 61, 63 and 69.
Reacted by Taylor Cramer and Dustin BensingBooking 71, 76 and 79. 😃
Reacted by Taylor Cramer and Dustin BensingI will take 55, 57, and 60
Reacted by Taylor Cramer and Dustin BensingI take 94 and 384 (I think there are no more available)
Reacted by Taylor Cramer, Dustin Bensing, Kevin Do and AdowrathMight I suggest folks just take on one or two issues, that way others wanting to learn, will have a chance to get involved too.
Reacted by Andrey, Stanislav Tkach, Dustin Bensing, Andréy Lesnikóv, Kelong Cong and Jesus Garlea@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.
Reacted by Luke Hinds, Andrey, Roy Brunton and Dustin BensingI'll gladly take 4 then
572 remaining items
Load more actions@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.
Reacted by Coder206Bonuses! There are also new bonuses if you want to work on a bonus
@jonathandturner Any free bonuses? I'd like to take one
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!
@jonathandturner I'll take 'Doesn't live long enough'
@jonathandturner Next time you update the list, I've completed the "EXXXX - Field unknown" bonus with #36798. Having a look at the others now.
@gavinb - great! It's updated
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)
I've almost done EXXXX - Fix temporary message and EXXXX - Doesn't live long enough, working on EXXXX - Better mutability
@jonathandturner Looks like all these are done except for the "bonus" bugs. Worth closing this issue?
Make a smaller one would be nice. I'll close once the new smaller one has been created.
@GuillaumeGomez I feel like this ticket can now be closed, as every action item has been taken care of.
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 uPlease file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.
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.
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.
cc @jonathandturner
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.