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
I wanted to bring up the idea of unpinning major dependencies. Upon comparing the latest releases, I noticed that version 0.27 is approximately 5 MB smaller than 0.26. This observation led me to question the overall size of the crate, primarily due to our major dependencies that might be commonly used across different projects.
By unpinning these major dependencies, we can allow users to utilize compatible versions available in their projects, potentially reducing the crate's size and optimizing resource usage. Of course, if a specific version of a dependency is crucial due to known bugs or other critical issues, it would make sense to keep it pinned.
For example, instead of pinning reqwest to v0.12.12, we could consider unpinning it to allow for any v0.12.x version. Given the nature of libraries like reqwest, it may not be necessary to pin each version for rigorous testing.
The text was updated successfully, but these errors were encountered:
Hello,
I wanted to bring up the idea of unpinning major dependencies. Upon comparing the latest releases, I noticed that version
0.27
is approximately 5 MB smaller than0.26
. This observation led me to question the overall size of the crate, primarily due to our major dependencies that might be commonly used across different projects.By unpinning these major dependencies, we can allow users to utilize compatible versions available in their projects, potentially reducing the crate's size and optimizing resource usage. Of course, if a specific version of a dependency is crucial due to known bugs or other critical issues, it would make sense to keep it pinned.
For example, instead of pinning
reqwest
tov0.12.12
, we could consider unpinning it to allow for anyv0.12.x
version. Given the nature of libraries like reqwest, it may not be necessary to pin each version for rigorous testing.The text was updated successfully, but these errors were encountered: