From: Rob Pike Date: Tue, 24 Jul 2018 22:26:01 +0000 (+1000) Subject: doc: fix a couple of drive-by review comments in FAQ X-Git-Tag: go1.11beta3~88 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=c1e1e882d2a1e474e21bc44edf26e3fb5ab87ebc;p=gostls13.git doc: fix a couple of drive-by review comments in FAQ Change-Id: I10cc2073e28cefb1b9a10c0ae89d819ad6417d66 Reviewed-on: https://go-review.googlesource.com/125695 Reviewed-by: Brad Fitzpatrick --- diff --git a/doc/go_faq.html b/doc/go_faq.html index f754dd3ce4..b1c15295d6 100644 --- a/doc/go_faq.html +++ b/doc/go_faq.html @@ -2419,12 +2419,12 @@ simpler because they don't need to specify how memory is managed across them.

This is not to say that the recent work in languages -like Rust that bring new ideas to the problem of to managing +like Rust that bring new ideas to the problem of managing resources is misguided; we encourage this work and are excited to see how it evolves. But Go takes a more traditional approach by addressing object lifetimes through -garbage collection, and garbage collection only. +garbage collection, and garbage collection alone.