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 | 7675081709bdb4c1fe00ab490f47074984770bfe (patch) | |
| tree | 8563f91b4e214a43159ae7e7bc1d6533f731d574 /doc | |
| parent | d6376e100ebb8bd97db3f7fabc5f18b9ce1bf8af (diff) | |
| download | go-7675081709bdb4c1fe00ab490f47074984770bfe.tar.gz | |
- added item to TODO list in go_spec
- filed a bug
R=r
OCL=15517
CL=15517
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/go_spec.txt | 2 |
1 files changed, 2 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 |