-
Notifications
You must be signed in to change notification settings - Fork 643
Allow '+' in keywords #5046
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
Allow '+' in keywords #5046
Conversation
For example: keywords = ["c++"].
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems reasonable on first glance, though I'd like to get a second opinion on this first.
@jtgeibel @carols10cents any thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think I could attend the next meeting so going to put +1 here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've manually tested the effects of this change on the UI and everything appears to work well :)
@dtolnay sorry that it took so long. it should be live in production now :) |
Thank you! Seems to work: https://crates.io/keywords/c++ |
Prior art: '+' in feature names — #2510. See that PR for the rationales in favor of that.
Specifically I would be interested in using "c++" as a tag on some of my FFI crates. Alphanumericizing it to "cpp" or "cxx" is not so good because those are each the name of a specific crate for a specific approach to C++ interop, and a crate that's generally suitable for C++ interop wouldn't want its keywords to imply it only works in concert with one of those two other crates.
Cargo has supported '+' in keywords since Rust 1.1.