Skip to content

E0449 needs to be updated to new format #35924

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
sophiajt opened this issue Aug 23, 2016 · 9 comments
Closed

E0449 needs to be updated to new format #35924

sophiajt opened this issue Aug 23, 2016 · 9 comments
Labels
A-diagnostics Area: Messages for errors, warnings, and lints E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@sophiajt
Copy link
Contributor

From: src/test/compile-fail/E0449.rs

E0449 needs a span_label and a span_note changed to a note, updating this:

error[E0449]: unnecessary visibility qualifier
  --> src/test/compile-fail/E0449.rs:17:1
   |
17 | pub impl Bar {} //~ ERROR E0449
   | ^^^^^^^^^^^^^^^
   |
note: place qualifiers on individual impl items instead
  --> src/test/compile-fail/E0449.rs:17:1
   |
17 | pub impl Bar {} //~ ERROR E0449
   | ^^^^^^^^^^^^^^^

To:

error[E0449]: unnecessary visibility qualifier
  --> src/test/compile-fail/E0449.rs:17:1
   |
17 | pub impl Bar {} //~ ERROR E0449
   | ^^^^^^^^^^^^^^^ `pub` not needed here
   |
   = note: place qualifiers on individual impl items instead

Bonus (though not sure if this is reasonable, but would be nice to try): let's underline the pub if we can.

error[E0449]: unnecessary visibility qualifier
  --> src/test/compile-fail/E0449.rs:17:1
   |
17 | pub impl Bar {} //~ ERROR E0449
   | ^^^ `pub` not needed here
   |
   = note: place qualifiers on individual impl items instead
@bstrie bstrie added the A-diagnostics Area: Messages for errors, warnings, and lints label Aug 24, 2016
@brson brson added the E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. label Aug 26, 2016
@alexispurslane
Copy link
Contributor

I'm working on fixing this.

@sophiajt
Copy link
Contributor Author

Ha, you beat me to it @ChristopherDumas

I was going to say that @nightlark signed up on the big list though at this point, since that list has been around so long, I'm starting to think we should do a free-for-all.

@nightlark
Copy link

nightlark commented Sep 13, 2016

I've been trying to use the bootstrap.py build system @jonathandturner, but the only way I've been able to get it to work is by getting rid of everything that has been compiled each time (basically getting a fresh copy of the repository each time, which takes a few hours to build). Are any changes needed to the arguments passed to bootstrap.py in order to get it to work? I'm using a Mac, and it looks like all of the minimum versions are met with respect to dependencies for compiling from source.

$ python src/bootstrap/bootstrap.py --step libstd --stage 1
Finished debug [unoptimized + debuginfo] target(s) in 0.0 secs
Synchronizing submodule url for 'src/compiler-rt'
Synchronizing submodule url for 'src/jemalloc'
Synchronizing submodule url for 'src/liblibc'
Synchronizing submodule url for 'src/llvm'
Synchronizing submodule url for 'src/rt/hoedown'
Synchronizing submodule url for 'src/rust-installer'
Unknown option: -C
usage: git [--version] [--help] [-c name=value]
[--exec-path[=]] [--html-path] [--man-path] [--info-path]
[-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
[--git-dir=] [--work-tree=] [--namespace=]
[]
command did not execute successfully: "git" "-C" "src/compiler-rt" "reset" "--hard"
expected success, got: exit code: 129

@sophiajt
Copy link
Contributor Author

@nightlark - that's strange. What version of git are you running?

This is what's on my mac:

$ git --version
git version 2.9.2

@sophiajt
Copy link
Contributor Author

@nightlark - working on a fix now: #36456

@nightlark
Copy link

@jonathandturner - I'm running version 1.8.4; thanks for the fix, I'll try it out. (And update if it still doesn't work).

@nightlark
Copy link

@ChristopherDumas did you already do this, or I can I still send my PR in?

@alexispurslane
Copy link
Contributor

No, I haven't done this. high school started and I forgot. Go ahead.

@bstrie
Copy link
Contributor

bstrie commented Sep 25, 2016

Freeing this one up as part of the final push for #35233.

bors added a commit that referenced this issue Sep 27, 2016
Update E0425, E0446, E0449

This addresses #35343, #35923, and #35924.  Part of #35233

Specifically, this adds labels to these error messages following the suggestions in the attached bugs.

r? @nrc
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

5 participants