From 6a3859f4331b2039142673e9beac8ffdd7d2628a Mon Sep 17 00:00:00 2001 From: Robert Griesemer Date: Mon, 20 May 2013 14:01:07 -0700 Subject: [PATCH] spec: removed old or invalid TODOs Several old TODOs are either resolved now (e.g. when is a return needed), or are from a time the language wasn't frozen (^ for uints only). Consolidated the others. R=golang-dev, r CC=golang-dev https://golang.org/cl/9599044 --- doc/go_spec.html | 31 +------------------------------ 1 file changed, 1 insertion(+), 30 deletions(-) diff --git a/doc/go_spec.html b/doc/go_spec.html index 0015cbfb5d..b3134eed83 100644 --- a/doc/go_spec.html +++ b/doc/go_spec.html @@ -15,6 +15,7 @@ TODO [ ] 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 --> @@ -2507,13 +2508,6 @@ p.M0() // ((*p).T0).M0() - - -

Index expressions

@@ -3337,13 +3331,6 @@ channel, or false if it is a zero value generated because the channel is closed and empty.

- -

Method expressions

@@ -3914,15 +3901,6 @@ context, even if it would be integral when calculated using infinite precision.

-

Order of evaluation

@@ -4901,13 +4879,6 @@ function. A "return" statement that specifies results sets the result parameters any deferred functions are executed.

-

Break statements

-- 2.50.0