mirror of https://github.com/golang/go.git
doc/go_faq.html: fix a couple of nits
Wrong article, one stylistic point that bothers someone (but not me). LGTM=bradfitz R=golang-codereviews, bradfitz CC=golang-codereviews https://golang.org/cl/156680043
This commit is contained in:
parent
ffa5e5f7fc
commit
a9422651f9
|
|
@ -1115,7 +1115,7 @@ error but the situation can still be confusing, because sometimes a
|
|||
<a href="#different_method_sets">pointer
|
||||
is necessary to satisfy an interface</a>.
|
||||
The insight is that although a pointer to a concrete type can satisfy
|
||||
an interface, with one exception <em>a pointer to an interface can never satisfy a interface</em>.
|
||||
an interface, with one exception <em>a pointer to an interface can never satisfy an interface</em>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -1356,7 +1356,7 @@ to speed it up.
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Go's goroutine scheduler is not as good as it needs to be. In future, it
|
||||
Go's goroutine scheduler is not as good as it needs to be. In the future, it
|
||||
should recognize such cases and optimize its use of OS threads. For now,
|
||||
<code>GOMAXPROCS</code> should be set on a per-application basis.
|
||||
</p>
|
||||
|
|
|
|||
Loading…
Reference in New Issue