News for hackers. Stuff that matters.
Re:A Proposal for Package Versioning in Go by steveklabnik on Tuesday March 27, 2018 @09:57AM (#16688368)
> It has another nice advantage over Rust's system - you have have pre-releases of major versions. Rust doesn't really have a way to do that except for releases before version 1.0.

Semver has a specific way to indicate that a feature is a pre-release, and people use it. The second post on /r/rust is advertising a pre-release of the next major version of rand: https://crates.io/crates/rand/0.5.0-pre.0

(Yes, this is before 1.0, but 1.5.0-pre.0 would work just fine too!)

Re:A Proposal for Package Versioning in Go by IshKebab on Tuesday March 27, 2018 @03:26PM (#16691915)
Do you have a reference for that? It isn't mentioned here: https://doc.rust-lang.org/cargo/reference/manifest.html#the-...

I found this bug report and it seems like it has some issues: https://github.com/rust-lang/cargo/issues/2222

Re:A Proposal for Package Versioning in Go by steveklabnik on Tuesday March 27, 2018 @04:04PM (#16692238)
Reference: I maintain the semver library. I’m on my phone, so I can’t link you to the docs right now. I’ll add a link tomorrow.
Re:A Proposal for Package Versioning in Go by steveklabnik on Wednesday March 28, 2018 @03:26AM (#16696064)
So, looking back, we don't explicitly say that we have these things, we just say that we use semver versions, and the semver spec specifies them. I've been meaning to re-vamp the cargo docs, maybe this is worth explicitly calling out. Thanks!
Re:A Proposal for Package Versioning in Go by IshKebab on Wednesday March 28, 2018 @08:56AM (#16697307)
Ah cool, sorry I wouldn't have asked for a reference if I'd noticed your username!
Re:A Proposal for Package Versioning in Go by steveklabnik on Wednesday March 28, 2018 @10:05AM (#16697694)
It's all good! <3