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
The users of this library (notably aleo and SnarkOS) are currently specifying snarkVM as a dependency by using a commit hash. This is incovenient since not only all users of the library need to update on each snarkVM merge, but also because it's very hard to keep track when a given change is being included or not (and whether a rev is newer or older than another). Additionally, at least until recently pulling dependencies by revision may be slower.
Semver could be used instead, doing explicit github releases or git tagging, improving dependency readability even if locks would still need to be updated to fetch the latest version. A lighter-weight, although more fragile, alternative to consider is to just point the user projects to the main branch of this repository.
The text was updated successfully, but these errors were encountered:
💥 Proposal
The users of this library (notably aleo and SnarkOS) are currently specifying snarkVM as a dependency by using a commit hash. This is incovenient since not only all users of the library need to update on each snarkVM merge, but also because it's very hard to keep track when a given change is being included or not (and whether a rev is newer or older than another). Additionally, at least until recently pulling dependencies by revision may be slower.
Semver could be used instead, doing explicit github releases or git tagging, improving dependency readability even if locks would still need to be updated to fetch the latest version. A lighter-weight, although more fragile, alternative to consider is to just point the user projects to the main branch of this repository.
The text was updated successfully, but these errors were encountered: