From: Robert Griesemer <gri@golang.org>
Date: Tue, 26 May 2015 18:44:18 +0000 (-0700)
Subject: spec: removed TODOs (invisible html comment) in favor of issues
X-Git-Tag: go1.5beta1~474
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=310fb9e8087471f6ab65d8c464df10572c0d38ed;p=gostls13.git

spec: removed TODOs (invisible html comment) in favor of issues

- no "visible" change to spec but for updated date
- retired several outdated TODO items
- filed non-urgent issues 10953, 10954, 10955 for current TODOs

Change-Id: If87ad0fb546c6955a6d4b5801e06e5c7d5695ea2
Reviewed-on: https://go-review.googlesource.com/10382
Reviewed-by: Ian Lance Taylor <iant@golang.org>
---

diff --git a/doc/go_spec.html b/doc/go_spec.html
index cdcca6be57..b5f18f3a02 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -1,24 +1,9 @@
 <!--{
 	"Title": "The Go Programming Language Specification",
-	"Subtitle": "Version of May 18, 2015",
+	"Subtitle": "Version of May 26, 2015",
 	"Path": "/ref/spec"
 }-->
 
-<!--
-TODO
-[ ] need language about function/method calls and parameter passing rules
-[ ] last paragraph of #Assignments (constant promotion) should be elsewhere
-    and mention assignment to empty interface.
-[ ] need to say something about "scope" of selectors?
-[ ] clarify what a field name is in struct declarations
-    (struct{T} vs struct {T T} vs struct {t T})
-[ ] need explicit language about the result type of operations
-[ ] should probably write something about evaluation order of statements even
-	though obvious
-[ ] in Selectors section, clarify what receiver value is passed in method invocations
--->
-
-
 <h2 id="Introduction">Introduction</h2>
 
 <p>