Skip to content

Can't use the same function from two different crates with the same name #2155

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.

Sign up for GitHub

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

Jump to bottom
Closed
brson opened this issue Apr 8, 2012 · 1 comment
Closed

Can't use the same function from two different crates with the same name #2155

brson opened this issue Apr 8, 2012 · 1 comment
Assignees
@brson
Labels
A-linkage Area: linking into static, shared libraries and binaries E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Apr 8, 2012

If I have crate B (vers = "0.1") and crate B (vers = "0.2") and they both contain function f and I use both crates, then I can't call function f from both crates because of name collisions. This is partly because of c83d61d (which I will revert), and partly because of other missing parts of the versioning story.
@ghost ghost assigned brson Apr 8, 2012
@brson brson mentioned this issue Apr 8, 2012
Closed
@brson
Copy link
Contributor Author

brson commented Apr 8, 2012

Fixed by d9070b4

@brson brson closed this as completed Apr 8, 2012
Kobzol pushed a commit to Kobzol/rust that referenced this issue Dec 29, 2024
@lcnr
closure constraints (rust-lang#2155)
f96f76a
Kobzol pushed a commit to Kobzol/rust that referenced this issue Dec 30, 2024
@lcnr
closure constraints (rust-lang#2155)
9f104cc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brson brson

Labels
A-linkage Area: linking into static, shared libraries and binaries E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brson