@izs I suspect a bunch of us getting together and talking this out would be reasonably productive. Cargo doubles down on compat guarantees.
-
-
@izs I suspect it will be easier to enforce with a typed language. Most of them time, if you violate semver, code won't compile. -
@wycats I still maintain that explicit range syntax is safer. If you say you want 1.6.3, get that. If you want guessing, use ^ to opt-in. -
@izs all dupes all the time only works when deps are only used internally. As soon as packages start sharing interfaces, kaboom. -
@wycats Yeah, but meh. Ostensibly that's what peerDeps are for, but I'd argue "sharing interfaces" is the fundamental reason peerDeps suck. -
.
@wycats "Sharing interfaces" is just "sharing state" in fancy clothes. -
@izs Not necessarily. In Cargo, "sharing interfaces" means "sharing static types"; no state involved. Useful to get a crisp understanding. -
@wycats@izs just like collecting doesn't mean searching?#restorethe4th -
- 1 more reply
New conversation -
-
-
@izs We disallow duplicates within major versions post-1.0 on the grounds that if you want 1.2 and I want 1.3, then 1.6.3 should work.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.