Warn about crates named with Rust keywords #2699
Labels
A-diagnostics
Area: Error and warning messages generated by Cargo itself.
Comments
alexcrichton
added
the
A-diagnostics
sbeckeriv
added a commit
to sbeckeriv/cargo
that referenced
this issue
May 17, 2016
Dearest Reviewer, This pull request extends the banned list of project names to include all of the current keywords for rust. I got the list of keywords from https://doc.rust-lang.org/grammar.html#keywords . This closes rust-lang#2699 . The original ticket said warn but I figured how test is handled is most likely how all banned names should be handled. Oddly enough a few keywords have made their way to the crates.io. fn and proc are both examples I found spot checking keywords. I do not there is any action to take on those crates. Thanks Becker
bors
added a commit
that referenced
this issue
May 17, 2016
Ban keywords from crate names Dearest Reviewer, This pull request extends the banned list of project names to include all of the current keywords for rust. I got the list of keywords from https://doc.rust-lang.org/grammar.html#keywords . This closes #2699 . The original ticket said warn but I figured how test is handled is most likely how all banned names should be handled. Oddly enough a few keywords have made their way to the crates.io. fn and proc are both examples I found spot checking keywords. I do not there is any action to take on those crates. Thanks Becker
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I made a crate called "pub", and was unable to import it into a dependent project because of the keyword clash. Some sort of warning or error from cargo would be appreciated.
The text was updated successfully, but these errors were encountered: