Manishearth namespacing-rfc issues

Manishearth / namespacing-rfc

RFC for Packages as Optional Namespaces

47 stars 3 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

What does `--extern foo::bar=bar.rlib` *actually* mean?

#21 jsgf closed 1 year ago
1
Crate vs package terminology

#20 jsgf closed 1 year ago
0
Cross-registry concerns

#19 CAD97 opened 1 year ago
1
How does dependency renaming interact with package namespacing?

#18 CAD97 opened 1 year ago
1
What happens when package.name != lib.name?

#17 CAD97 opened 1 year ago
1
Allow a domain namespace.

#16 mehmooda closed 3 years ago
1
Cross-registry dependencies are not permitted for experimental registry

#15 jplatte opened 3 years ago
2
Can't download namespaced crates

#14 jplatte opened 3 years ago
0
Timeout was reached when trying to upload a crate

#13 jplatte closed 3 years ago
1
[implementation] `cargo new --lib "foo/bar"` doesn't work

#12 Manishearth opened 3 years ago
9
Fixes a broken link

#11 colindean closed 3 years ago
0
Prototype using `/` available for testing out!

#10 carols10cents opened 3 years ago
6
Does a namespace have to exist before publishing crates in that namespace?

#9 JWorthe opened 3 years ago
2
Unresolved: How many levels of crate-namespace nesting is allowed?

#8 carols10cents opened 3 years ago
4
Drawback: Names in code not matching names in, say, docs.rs could become required to have a namespace

#7 carols10cents opened 3 years ago
1
Drawback: Namespace root token

#6 Manishearth opened 3 years ago
0
Drawback: Slow migration

#5 Manishearth opened 3 years ago
1
Unresolved: Feature syntax

#4 Manishearth opened 3 years ago
5
Drawback: typosquatting

#3 Manishearth opened 3 years ago
10
Decision: Separator mapping

#2 Manishearth closed 2 years ago
8
Decision: Separator choice

#1 Manishearth closed 2 years ago
34