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

[Feature Request] [Package System] Need a way to solve conflicts around different versions of the standard libraries #13326

Closed
fEst1ck opened this issue May 17, 2024 · 0 comments · Fixed by #13318
Assignees
Labels
enhancement New feature or request

Comments

@fEst1ck
Copy link
Contributor

fEst1ck commented May 17, 2024

🚀 Feature Request

We Need a way to solve conflicts around (transitively) depending on different versions of the standard libraries.

Motivation

Developers have been struggling with the following situation. Suppose I am developing a package P1 that uses some new features of Aptos Framework in the dev version, and we also import another package P2 that relies on the mainnet version of Aptos Framework. However, this is not allowed by the current package system. The package system maintains a global scope and addresses each dependency package by only the package name, and different versions of the same package will result in conflicting package names.

@fEst1ck fEst1ck added the enhancement New feature or request label May 17, 2024
@fEst1ck fEst1ck self-assigned this May 17, 2024
@fEst1ck fEst1ck changed the title [Feature Request] [Package System] Need a way to depend on different versions of standard libraries [Feature Request] [Package System] Need a way to solve conflicts around different versions of the standard libraries May 17, 2024
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Move Language and Runtime Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant