Replacment of `-` vs `_` in package names inconsistent
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15.5k
- Forks
- 3k
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 51
Description
In the docs the behavior of replacement of dashes (-) vs underscore (_) is not as described. See https://github.com/bytecodealliance/cargo-component/issues/250#issuecomment-1979577958 for details.
Seems related to:
Overall I've always found the lib.name key to be super confusing because it adds to the dashes-vs-underscore ambiguity, which sometimes crops up with crates which use dashes in package.name and underscores in lib.name and while that kind of works it doesn't always work because now you need to use lib.name for specifying patches.
Originally posted by in https://github.com/rust-lang/cargo/issues/6827#issuecomment-480609592
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the The name field section in src/doc/src/reference/cargo-targets.md and compare its description with the details in the linked cargo-component issue comment. Clarify the documented dash-versus-underscore behavior and the related lib.name ambiguity; done when the reference matches the observed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100