Skip to content
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

RFC: Packages as (optional) namespaces #3243

Merged
merged 36 commits into from
Mar 11, 2024
Merged
Changes from 1 commit
Commits
Show all changes
36 commits
Select commit Hold shift + click to select a range
e590c72
Copy over RFC text from https://github.com/Manishearth/namespacing-rfc/
Manishearth Mar 9, 2022
5e6ad7c
Fix template
Manishearth Mar 9, 2022
d9d1556
Add basic FAQ
Manishearth Mar 9, 2022
e29aa55
Add more separator options
Manishearth Mar 9, 2022
3a0b099
leaf crate names
Manishearth Mar 10, 2022
4422adf
sep choice
Manishearth Mar 10, 2022
24db227
Clarify motivation on projects vs organizations
Manishearth Mar 10, 2022
1986c3d
Switch to colons
Manishearth Mar 25, 2022
42046f8
fixes
Manishearth Mar 26, 2022
2fff101
Document Python prior art
epage Mar 26, 2022
8e667ce
Expand on the guide-level explanation
epage Mar 26, 2022
01d37b2
Document feature flags drawbacks
epage Mar 26, 2022
4501047
Merge pull request #4 from epage/guide
Manishearth Mar 27, 2022
1f62468
Merge pull request #3 from epage/prior
Manishearth Mar 27, 2022
1ca3e62
Merge pull request #5 from epage/flags
Manishearth Mar 27, 2022
f7be349
Fix a couple of typos
epage Mar 28, 2022
9a144fb
Updaet motivation for `::` semantics
epage Mar 28, 2022
a578a67
Merge pull request #7 from epage/motivation
Manishearth Mar 28, 2022
3396a2e
Merge pull request #6 from epage/typos
Manishearth Mar 28, 2022
11c6354
Update summary to focus on `::` semantics
epage Mar 29, 2022
cc5872d
Merge pull request #8 from epage/summary
Manishearth Mar 29, 2022
65f7083
add renames as unresolved q
Manishearth Mar 29, 2022
5c497c5
fix syntax
Manishearth May 24, 2023
67ef913
fixes
Manishearth May 24, 2023
56fae2e
trie-unresolved
Manishearth May 24, 2023
482fae8
Update 0000-packages-as-optional-namespaces.md
Manishearth Jul 23, 2023
4c14f9c
Update text/0000-packages-as-optional-namespaces.md
Manishearth Nov 4, 2023
d9a3c90
Update text/0000-packages-as-optional-namespaces.md
Manishearth Nov 4, 2023
8bd7fbc
Add .crate file as unresolved
epage Nov 13, 2023
abde93f
Be explicit that open questions are deferred out
epage Nov 13, 2023
7d77485
Call out distributions
epage Nov 13, 2023
75dd867
Merge pull request #9 from epage/unresolved
Manishearth Nov 13, 2023
0db096f
Update text/0000-packages-as-optional-namespaces.md
Manishearth Mar 11, 2024
6cc8886
Rename 0000-packages-as-optional-namespaces.md to 3243-packages-as-op…
oli-obk Mar 11, 2024
a93b1e4
Add RFC PR link
oli-obk Mar 11, 2024
656203f
Link to rust tracking issue
oli-obk Mar 11, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update text/0000-packages-as-optional-namespaces.md
Co-authored-by: Eric Huss <eric@huss.org>
  • Loading branch information
Manishearth and ehuss authored Nov 4, 2023
commit 4c14f9c4cfe43d43286fbf617ddd28f1cf9417bd
2 changes: 1 addition & 1 deletion text/0000-packages-as-optional-namespaces.md
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@ One thing that could mitigate `foo/bar` mapping to the potentially ambiguous `fo

### Using identical syntax in Cargo.toml and Rust source

The `/` proposal does not require changes to Rust compiler to allow slash syntax (or whatever) to parse as a Rust path. Such changes could be made (though not with slash syntax due to parsing ambiguity, see [below](#Separator choice) for more options); this RFC is attempting to be minimal in its effects on rustc.
The `/` proposal does not require changes to Rust compiler to allow slash syntax (or whatever) to parse as a Rust path. Such changes could be made (though not with slash syntax due to parsing ambiguity, see [below](#separator-choice) for more options); this RFC is attempting to be minimal in its effects on rustc.

However, the divergence between Cargo.toml and rustc syntax does indeed have a complexity cost, and may be confusing to some users. Furthermore, it increases the chances of [Dash typosquatting](#Dash typosquatting) being effective.
Manishearth marked this conversation as resolved.
Show resolved Hide resolved

Expand Down