You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Package IDs, parsing and generating both "name-only" and "URL"
Publish support including index file system layout
Unresolved Issues
For an implicit bin in a namespaced package, should do something (e.g. warn, error) about cross-platform hazard of :: being in the name?
Future Extensions
No response
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
The text was updated successfully, but these errors were encountered:
feat: Add 'open-namespaces' feature
### What does this PR try to resolve?
This is a step towards #13576
### How should we test and review this PR?
### Additional information
Summary
RFC: #3243
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#my-feature
rustc tracking issue: rust-lang/rust#122349
crates.io tracking issue: rust-lang/crates.io#8292
Allow a parent package to open its API namespace for other packages to participate
Implementation
::
in the middle of package names, prevent publish (feat: Add 'open-namespaces' feature #13591)lib.name
puts it in a namespaceUnresolved Issues
::
being in the name?Future Extensions
No response
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
The text was updated successfully, but these errors were encountered: