3 ms·
Seems like identifying your library with a git tag would drop that risk to zero. I guess what I'm not understanding here is the utility. Why is it useful to in
by flir 3y ago
Seems like identifying your library with a git tag would drop that risk to zero.
I guess what I'm not understanding here is the utility. Why is it useful to include multiple versions of a library in a project? Is this a limitation I've been coding around without knowing it?
- celeritascelery 3y agoHave you ever had problem where two of your dependencies are each using a different version of the same library? Or have you ever wanted to incrementally upgrade an API so that you don’t have to change your entire code base in one fell swoop? That is where things like Unison or scrapscript can make it very easy.
- flir 3y agoOk, I can see "incremental upgrade" as a use-case. Thanks.
- penteract 3y agoOne reason for multiple versions of a library in a project is that the project wants to use 2 different dependencies, which themselves depend on incompatible versions of a third library.
- flir 3y agook, yep, that's one I've had myself. Thanks.
- cnity 3y agoI recommend reading the benefits section in the Unison docs[0]. 0: https://www.unison-lang.org/docs/the-big-idea/#benefits https://www.unison-lang.org/docs/the-big-idea/#benefits
- computerfriend 3y agoTags are not immutable.