commit | e7bea8f1d64fb6752bf603c5c6f39f12f99fc3a3 | [log] [tgz] |
---|---|---|
author | Dmitri Shuralyov <dmitshur@golang.org> | Sat May 06 15:59:30 2023 -0400 |
committer | Gopher Robot <gobot@golang.org> | Wed May 17 15:46:18 2023 +0000 |
tree | 33f5d005830b143f6386bf489ad1b464e1b84e11 | |
parent | ad6fd61f94f8fdf6926f5dee6e45bdd13add2f9f [diff] |
modfile: use semantic sort for exclude blocks For golang/go#60028. Change-Id: I4c7a726a900fc7c4b34816eba5cfd0361c45315f Reviewed-on: https://go-review.googlesource.com/c/mod/+/492990 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Bryan Mills <bcmills@google.com>
This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves.
It is NOT about supporting general development tools that need to do things like load packages in module mode. That use case, where modules are incidental rather than the focus, should remain in x/tools, specifically x/tools/go/packages.
The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.