Uh oh!
There was an error while loading. Please reload this page.
implements issue #2356 - #3252
Conversation
catamorphism
commented
Aug 23, 2012
@Vincent-Belliard -- Thanks for the patch! The first thing I'm noticing is that you're using |
catamorphism
commented
Aug 23, 2012
By the way, there's a style guide at https://github.com/mozilla/rust/wiki/Note-style-guide but it's still pretty sketchy at the moment. |
Vincent-Belliard
commented
Aug 23, 2012
I use for loops now. I just left the first while because we need to I read the few style guides I found but there are not too many things On 08/23/2012 09:35 PM, Tim Chevalier wrote:
|
catamorphism
commented
Aug 25, 2012
@Vincent-Belliard : Looks great for the most part! I made a few comments as line-by-line notes on your two commits. Since there are a few issues to fix, I figured I would let you fix them and submit a new commit -- if it was just a matter of rebasing off HEAD, I would do it myself, but it's a bit more involved. Hopefully my comments are understandable -- if not, just ask (or find me on IRC -- my nick there is Sorry this has turned out to be a bit involved, but if you fix the (minor) issues and resubmit a commit -- preferable combining the two commits into a single one -- I'll merge it. Thanks! |
Vincent-Belliard
commented
Aug 25, 2012
I modified the commit to include all you remarks. I rebased it against head of incoming. Thank you for for taking some of your time to help me beginning with Rust. |
catamorphism
commented
Aug 25, 2012
Merged, thank you! |
catamorphism
commented
Aug 25, 2012
Sorry, forgot one more thing: I'll add it myself in this case, but in general, every commit should come with a regression test that ensures that the change that was made behaves correctly. Occasionally this would be difficult, but usually it's not hard. |
We handle these adequately as of 0cc4b24. Resolves: rust-lang#77
3252: Improve integration with token color configuration r=matklad a=eaglgenes101 First, the extension now checks theme token color customizations as well as global token color customizations when determining what colors to highlight syntax with. Theme token color customizations take precedence over both global token color customizations and the theme token colors. Second, a few additional token color customization keys used by other themes are added. The original paths still take precedence, but now turning on rust analyzer syntax highlighting should now not unexpectedly homogenize token colors when custom themes are used. Co-authored-by: eaglgenes101 <eaglgenes101@gmail.com>
This commit modify the error message when an identifier is not found but it can be found in the class.
The old message was:
issue_2356.rs:22:16: 22:21 error: unresolved name: xyzt
The new message is:
issue_2356.rs:22:16: 22:20 error: unresolved name: xyzt.Did you mean: self.xyzt
I started looking at rust sources yesterday. It's my first commit which modify the sources. I hope I followed all the coding rules.