Commit db3f52db authored by Leigh McCulloch's avatar Leigh McCulloch Committed by Ian Lance Taylor

go/types: correct misspelling in function doc

The indirectType function comment uses the phrase 'layed out'. In the
context of that phrase, where something is being placed or sprawled,
the word should be 'laid'. 'Layed' is a misspelling of 'laid'.

Change-Id: I05ecb97637276e2252c47e92a0bd678130714889
GitHub-Last-Rev: 6ee67371b42c12ceaf4c6c245319748008ac7e7b
GitHub-Pull-Request: golang/go#27444
Reviewed-on: https://go-review.googlesource.com/132779Reviewed-by: default avatarIan Lance Taylor <iant@golang.org>
parent 67ac554d
...@@ -132,7 +132,7 @@ func (check *Checker) definedType(e ast.Expr, def *Named) (T Type) { ...@@ -132,7 +132,7 @@ func (check *Checker) definedType(e ast.Expr, def *Named) (T Type) {
// indirectType is like typ but it also breaks the (otherwise) infinite size of recursive // indirectType is like typ but it also breaks the (otherwise) infinite size of recursive
// types by introducing an indirection. It should be called for components of types that // types by introducing an indirection. It should be called for components of types that
// are not layed out in place in memory, such as pointer base types, slice or map element // are not laid out in place in memory, such as pointer base types, slice or map element
// types, function parameter types, etc. // types, function parameter types, etc.
func (check *Checker) indirectType(e ast.Expr) Type { func (check *Checker) indirectType(e ast.Expr) Type {
check.push(indir) check.push(indir)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment