Apparently we use the spec of the latest released version here (which is the Go 1.17 spec). But given that we show the first generics tutorial among the documentation, I think we should show the latest (in-progress) version of the spec as well. While the spec is incomplete, many new sections have been written which are complete and are relevant for understanding generics (e.g., new syntax, interfaces as type sets, and new rules for assignments and conversions).

I think for the next two months it's OK to point people to https://tip.golang.org/ref/spec.

I agree with Ian, and think this is working as intended.
https://go.dev/ref/spec allows users to view the specification for the currently stable Go language version.
https://tip.golang.org/ref/spec allows previewing upcoming changes, which might be evolving.
When the final Go 1.18 is released, the content at https://tip.golang.org/ref/spec will become visible at https://go.dev/ref/spec. This happens as part of the release process, so there's nothing we need to do explicitly to make it happen.

Blog posts and tutorials can link to https://tip.golang.org/ref/spec now, and that link can be simplified to "/ref/spec" after 1.18 is out.

I'll close this issue to help keep the list of 1.18 release-blocking issues actionable. @griesemer Please comment or re-open if you think there's something we need to do before 1.18 can be released.