diff options
author | Robert Griesemer <gri@golang.org> | 2008-09-18 23:16:22 -0700 |
---|---|---|
committer | Robert Griesemer <gri@golang.org> | 2008-09-18 23:16:22 -0700 |
commit | dc9e4d29ecd30e5453ffa1987d7890b47c571a33 (patch) | |
tree | 8563f91b4e214a43159ae7e7bc1d6533f731d574 | |
parent | 56250e6784166b83288f8727d66594a38e866491 (diff) | |
download | golang-dc9e4d29ecd30e5453ffa1987d7890b47c571a33.tar.gz |
- added item to TODO list in go_spec
- filed a bug
R=r
OCL=15517
CL=15517
-rw-r--r-- | doc/go_spec.txt | 2 | ||||
-rw-r--r-- | test/bugs/bug103.go | 14 |
2 files changed, 16 insertions, 0 deletions
diff --git a/doc/go_spec.txt b/doc/go_spec.txt index c82919272..9561e924a 100644 --- a/doc/go_spec.txt +++ b/doc/go_spec.txt @@ -52,6 +52,8 @@ Open issues according to gri: [ ] iant suggests to use abstract/precise int for len(), cap() - good idea (issue: what happens in len() + const - what is the type?) [ ] Do composite literals create a new literal each time (gri thinks yes) +[ ] should binary <- be at lowest precedence level? when is a send/receive non-blocking? +[ ] consider syntactic notation for composite literals to make them parseable w/o type information --> Contents diff --git a/test/bugs/bug103.go b/test/bugs/bug103.go new file mode 100644 index 000000000..c350a53bb --- /dev/null +++ b/test/bugs/bug103.go @@ -0,0 +1,14 @@ +// errchk $G $D/$F.go + +// Copyright 2009 The Go Authors. All rights reserved. +// Use of this source code is governed by a BSD-style +// license that can be found in the LICENSE file. + +package main + +func f() /* no return type */ {} + +func main() { + x := f(); // should not compile +} + |