qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-23 00:20:12 -07:00
Code Releases Activity

doc: fix a couple of drive-by review comments in FAQ

Browse Source 
Change-Id: I10cc2073e28cefb1b9a10c0ae89d819ad6417d66
Reviewed-on: https://go-review.googlesource.com/125695
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This commit is contained in:
Rob Pike 2018-07-25 08:26:01 +10:00
parent 7bebc6b722
commit c1e1e882d2
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/go_faq.html
View File

@ -2419,12 +2419,12 @@ simpler because they don't need to specify how memory is managed across them.
<p>
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.
</p>
<p>