Prevent conflicts with uber-go/atomic.

[zmt]

No description provided.

[abhinav]

I wouldn't do this. Right now, the "you must use go.uber.org/atomic" restriction applies only to users of Go modules. Adding the canonical import directive will break users of the library in legacy ecosystems (dep and glide) that are using the old supported import path (uber-go/atomic).

[codecov]

Codecov Report

Merging #59 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #59   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           3      3           
  Lines         145    145           
=====================================
  Hits          145    145

Impacted Files	Coverage Δ
atomic.go	100% <ø> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fb77e1d...f5fbbf1. Read the comment docs.

[prashantv]

+1 to @abhinav , see #36 and #13 (comment)

I think requiring go.uber.org/atomic to go modules users is the best tradeoff.

[abhinav]

Closing because,

• we don't want to break legacy ecosystems
• users of Go modules get this automatically
• users of Go modules using the legacy import path need to use instructions from README: Fix legacy import path instructions #60