diff options
Diffstat (limited to 'content/using-go-modules.article')
| -rw-r--r-- | content/using-go-modules.article | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/content/using-go-modules.article b/content/using-go-modules.article index ea13545..8d2774a 100644 --- a/content/using-go-modules.article +++ b/content/using-go-modules.article @@ -48,7 +48,6 @@ Starting in Go 1.13, module mode will be the default for all development. This post walks through a sequence of common operations that arise when developing Go code with modules: - - Creating a new module. - Adding a dependency. - Upgrading dependencies. @@ -161,7 +160,6 @@ Now let’s run the test again: ok example.com/hello 0.023s $ - The `go` command resolves imports by using the specific dependency module versions listed in `go.mod`. When it encounters an `import` of a package not provided @@ -195,7 +193,6 @@ modules are cached locally (in `$GOPATH/pkg/mod`): ok example.com/hello 0.020s $ - Note that while the `go` command makes adding a new dependency quick and easy, it is not without cost. Your module now literally _depends_ on the new dependency @@ -377,7 +374,6 @@ Then we can test our code: ok example.com/hello 0.024s $ - Note that our module now depends on both `rsc.io/quote` and `rsc.io/quote/v3`: $ go list -m rsc.io/q... @@ -468,7 +464,6 @@ so we can undo that: return quote.Concurrency() } - Let's re-run the tests to make sure everything is working: $ go test |