1
0
mirror of https://github.com/golang/go synced 2024-11-11 23:20:24 -07:00

doc/go1.18: mention fuzzing in the release notes

Also make a few small formatting fixes.

Change-Id: Iad99d030312393af3b6533f2cd00f09aea0f2a7d
Reviewed-on: https://go-review.googlesource.com/c/go/+/369074
Trust: Katie Hockman <katie@golang.org>
Run-TryBot: Katie Hockman <katie@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Robert Griesemer <gri@golang.org>
This commit is contained in:
Katie Hockman 2021-12-03 12:23:44 -05:00
parent d921bb21df
commit deb988a286

View File

@ -59,9 +59,9 @@ Do not send CLs removing the interior tags from such phrases.
<h3 id="generics">Generics</h3>
<p>
Go 1.18 includes an implementation of generics as described
by <a href="https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md">the
proposal</a>.
Go 1.18 includes an implementation of generics as described
by <a href="https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md">the
generics proposal</a>.
</p>
<p>
@ -74,6 +74,27 @@ proposal</a>.
</ul>
</p>
<h3 id="fuzzing">Fuzzing</h3>
<p>
Go 1.18 includes an implementation of fuzzing as described by
<a href="https://golang.org/issue/44551">the fuzzing proposal</a>.
</p>
<p>
See the <a href="https://go.dev/doc/fuzz">fuzzing landing page</a> to get
started.
</p>
<p>
Please be aware that fuzzing can consume a lot of memory and may impact your
machines performance while it runs. Also be aware that the fuzzing engine
writes values that expand test coverage to a fuzz cache directory within
<code>$GOCACHE/fuzz</code> while it runs. There is currently no limit to the
number of files or total bytes that may be written to the fuzz cache, so it
may occupy a large amount of storage (possibly several GBs).
</p>
<h2 id="ports">Ports</h2>
<h3 id="amd64">AMD64</h3>