Chapter 2 · Practice 3 of 4
Check which version the docs and examples target
Why it matters
Technologies change, and much of the advice online is for older versions. Even official guides can lag: Effective Go carries a note that it was written for Go's release in 2009, is not actively updated, and does not cover significant later changes such as generics and modules.
Habits that save hours:
- Note the version you are learning (the current Rust Book, for example, states the Rust version and edition it assumes).
- Read the release notes for recent major versions to learn what changed.
- Check dates on blog posts and answers, and prefer ones that match your version.
- Match your local setup to the version in the tutorial.
Do
- Read the release notes for the last major version
- Check the date on every third-party answer
Avoid
- Following an old tutorial against a new version and fighting the differences