The change does not affect either the Go language or the way that you compile the code or fetch dependencies, what's the problem?

Go is much more stable than Rust, you know how many Rust libs need nighlty to work?

> Go is much more stable than Rust, you know how many Rust libs need nighlty to work?

Rust libs that use nightly do so because they're opting in to new features, not because released features are unstable.

Even then with the releases of const generics, proc macros, and a couple other big-ticket features, fewer and fewer Rust projects require nightly anyway.

How many do? Which ones? I’m curious what you’re still running into.

(This is me being curious about your Rust comment, not implying anything about the relative stability of the two languages)

For example: https://github.com/rust-lang/rustfmt

rustfmt is not a library, and folks don’t depend on it as one. The only nightly features it uses are “hey let me use compiler as a library please,” which is also not, in my experience, common in the ecosystem. Even furthermore, it’s distributed precompiled in your rust installation, so that doesn’t end up giving you a nightly dependency to use it.

Anyway, thanks. Nightly does exist to be used, but our users largely report using stable, so when people say things like this, I am trying to see if there’s any blind spots.