Skip to content

Highlight rustc's warning/errors in bright-white, similar to Clang #7640

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

Closed
wants to merge 1 commit into from
Closed

Conversation

kud1ing
Copy link

@kud1ing kud1ing commented Jul 7, 2013

Currently on Mac OS X this is shown rather in light-gray though. Maybe a bug in term.rs?
Ping @cmr

@emberian
Copy link
Member

emberian commented Jul 7, 2013

@kud1ing if it's light gray it's because your TERM only advertises 8 colors, the terminal library won't use a color the terminal doesn't advertise in the terminfo (it's probably xterm, it should be xterm-256color or somesuch)

@kud1ing
Copy link
Author

kud1ing commented Jul 8, 2013

Thanks, i wonder what clang does differently.

@thestinger
Copy link
Contributor

Landing as part of #7657.

@thestinger thestinger closed this Jul 8, 2013
@lilyball
Copy link
Contributor

Clang doesn't highlight errors in bright white. It highlights errors in bold. It's only bright white for you because your foreground color is white.

@kud1ing
Copy link
Author

kud1ing commented Jul 10, 2013

ok

@alexcrichton
Copy link
Member

cc #7737, this has made my error messages very sad :(

@lilyball
Copy link
Contributor

PR #7716 fixes this.

flip1995 pushed a commit to flip1995/rust that referenced this pull request Sep 28, 2021
…teffen

Improve accuracy of `mut_key`

Fixes rust-lang#6745.

Whilst writing the tests for this, I noticed what I believe is a false negative (the code in `@xFrednet's` [comment](rust-lang/rust-clippy#6745 (comment)) doesn't trigger the lint).  Currently the tests contain a case for this (which is blatantly ignored), but I'm not at all sure how to implement this (since the lint currently behaves completely differently for ADTs).  I'm not sure what should be done - on the one hand the extra test cases are misleading, but on the other hand they don't cause much harm and would save effort for anyone fixing that false negative.

---

changelog: Improve accuracy of `clippy::mutable_key_type`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants