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
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.
The text was updated successfully, but these errors were encountered:
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
🚀 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 packageP2
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.The text was updated successfully, but these errors were encountered: