aboutsummaryrefslogtreecommitdiff
path: root/content/introducing-gofix.article
diff options
context:
space:
mode:
authorBrad Fitzpatrick <bradfitz@golang.org>2018-04-13 19:58:08 +0000
committerBrad Fitzpatrick <bradfitz@golang.org>2018-04-13 20:25:50 +0000
commit6788987eaeb886066958855e0dd2b12778204543 (patch)
treea830ab11aad55293f6e3d294538d9332c43754c2 /content/introducing-gofix.article
parent7edc962a942e4a9d5e06dde79299f7fc5605f000 (diff)
content: change more links from http to https
talks.golang.org blog.golang.org godoc.org swtch.com And few misc ones done by hand. Change-Id: Ia2c4fee630814a1ef3b143098bbac3edd6a45064 Reviewed-on: https://go-review.googlesource.com/106977 Reviewed-by: Andrew Bonventre <andybons@golang.org>
Diffstat (limited to 'content/introducing-gofix.article')
1 files changed, 1 insertions, 1 deletions
diff --git a/content/introducing-gofix.article b/content/introducing-gofix.article
index 98b7b80..5b42b5b 100644
--- a/content/introducing-gofix.article
+++ b/content/introducing-gofix.article
@@ -6,7 +6,7 @@ Russ Cox
* Introduction
-The next Go release will include significant API changes in several fundamental Go packages. Code that [[http://codereview.appspot.com/4239076][implements an HTTP server handler]], [[http://codereview.appspot.com/4244055][calls `net.Dial`]], [[http://codereview.appspot.com/4357052][calls `os.Open`]], or [[http://codereview.appspot.com/4281055][uses the reflect package]] will not build unless it is updated to use the new APIs. Now that our releases are [[http://blog.golang.org/2011/03/go-becomes-more-stable.html][more stable and less frequent]], this will be a common situation. Each of these API changes happened in a different weekly snapshot and might have been manageable on its own; together, however, they represent a significant amount of manual effort to update existing code.
+The next Go release will include significant API changes in several fundamental Go packages. Code that [[http://codereview.appspot.com/4239076][implements an HTTP server handler]], [[http://codereview.appspot.com/4244055][calls `net.Dial`]], [[http://codereview.appspot.com/4357052][calls `os.Open`]], or [[http://codereview.appspot.com/4281055][uses the reflect package]] will not build unless it is updated to use the new APIs. Now that our releases are [[https://blog.golang.org/2011/03/go-becomes-more-stable.html][more stable and less frequent]], this will be a common situation. Each of these API changes happened in a different weekly snapshot and might have been manageable on its own; together, however, they represent a significant amount of manual effort to update existing code.
[[https://golang.org/cmd/fix/][Gofix]] is a new tool that reduces the amount of effort it takes to update existing code. It reads a program from a source file, looks for uses of old APIs, rewrites them to use the current API, and writes the program back to the file. Not all API changes preserve all the functionality of an old API, so gofix cannot always do a perfect job. When gofix cannot rewrite a use of an old API, it prints a warning giving the file name and line number of the use, so that a developer can examine and rewrite the code. Gofix takes care of the easy, repetitive, tedious changes, so that a developer can focus on the ones that truly merit attention.