|author||Jay Conrod <firstname.lastname@example.org>||Thu Mar 11 16:54:44 2021 -0500|
|committer||Jay Conrod <email@example.com>||Fri Apr 09 13:44:25 2021 +0000|
modfile: parse deprecation notices in module comments Deprecation notices start with "Deprecated:" at the beginning of a line and run until the end of the paragraph. This CL reuses text extraction code for retraction rationale, so the same rules apply: comment text may be from the comments above a "module" directive or as a suffix on the same line. For golang/go#40357 Change-Id: Id5524149c6bbda3effc64c6b668b701b5cf428af Reviewed-on: https://go-review.googlesource.com/c/mod/+/301089 Trust: Jay Conrod <firstname.lastname@example.org> Run-TryBot: Jay Conrod <email@example.com> TryBot-Result: Go Bot <firstname.lastname@example.org> Reviewed-by: Bryan C. Mills <email@example.com> Reviewed-by: Michael Matloob <firstname.lastname@example.org>
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.