5 ms·
There's a very little overlap between the purpose and use case of the two projects. There's not that many good, short names. I personally wouldn't worry about n
by tomashubelbauer 7y ago
There's a very little overlap between the purpose and use case of the two projects. There's not that many good, short names. I personally wouldn't worry about naming conflicts with another project, unless it was a similar project in more than a name.
- fnord123 7y agohttps://github.com/rxRust/rxRust https://github.com/rxRust/rxRust Many Rust projects are blah-rs where the rs is dropped in the crate name. So it would be normal to be confused and think Rx == RxRust. e.g. https://github.com/rust-lang/futures-rs https://github.com/rust-lang/futures-rs has crate name "futures". >There's not that many good, short names. There'd be loads if the Rust community (or.. the 'rust parliamentary community' (people who actually get involved in the RFC processes and see things through to the end (heroes, imo)) (cf PLP[0])) elected to use namespaces for crates. [0] https://en.wikipedia.org/wiki/Parliamentary_Labour_Party https://en.wikipedia.org/wiki/Parliamentary_Labour_Party
- tomashubelbauer 7y agoNamespaces are a good idea on paper, but you still need to secure the non namespaced name when you reach a bit of popularity or someone else will who will push malware there knowing people will often add a crate by the name they think it has and not necessarily the one it has.
- fnord123 7y agoNon namespaced crates can be io.cargo.blah and the short name can be deprecated or even changed programatically.
- HelloNurse 7y agoShort names are bad, unless somewhat sheltered from confusion (e.g. brief names of command line tools, which need to be unique only within your PATH environment variable and your installed man pages, not on the web).
- fnord123 7y agoAbsolutely. And even ls, sed, etc are in the coreutils package. Not 'ls' package.