- 27 Jan, 2012 10 commits
-
-
Ivan Krasin authored
R=rsc, gri CC=golang-dev https://golang.org/cl/5577061
-
Brad Fitzpatrick authored
Fixes #2747 R=golang-dev, gri, r, rogpeppe, r CC=golang-dev https://golang.org/cl/5564065
-
Rémy Oudompheng authored
R=golang-dev, rsc CC=golang-dev https://golang.org/cl/5569074
-
Dmitriy Vyukov authored
+eliminates a possibility of sending a call to Done several times. +fixes memory leak in case of temporal Write errors. +fixes data race on Client.shutdown. +fixes data race on Client.closing. +fixes comments. Fixes #2780. R=r, rsc CC=golang-dev, mpimenov https://golang.org/cl/5571063
-
Ian Lance Taylor authored
complit1.go:37:34: error: may only omit types within composite literals of slice, array, or map type complit1.go:38:19: error: may only omit types within composite literals of slice, array, or map type complit1.go:18:21: error: slice of unaddressable value complit1.go:19:10: error: slice of unaddressable value complit1.go:20:9: error: slice of unaddressable value convert1.go:28:13: error: invalid type conversion convert1.go:32:12: error: invalid type conversion (cannot use type string as type Tint64) convert1.go:36:12: error: invalid type conversion convert1.go:37:13: error: invalid type conversion convert1.go:40:11: error: invalid type conversion convert1.go:41:12: error: invalid type conversion convert1.go:44:12: error: invalid type conversion convert1.go:46:13: error: invalid type conversion convert1.go:48:11: error: invalid type conversion convert1.go:50:12: error: invalid type conversion convert1.go:52:6: error: invalid type conversion convert1.go:53:12: error: invalid type conversion convert1.go:54:12: error: invalid type conversion convert1.go:56:13: error: invalid type conversion convert1.go:57:11: error: invalid type conversion convert1.go:58:11: error: invalid type conversion convert1.go:64:13: error: invalid type conversion convert1.go:68:12: error: invalid type conversion (cannot use type Tstring as type Tint64) convert1.go:72:12: error: invalid type conversion convert1.go:73:13: error: invalid type conversion convert1.go:76:11: error: invalid type conversion (cannot use type Tbyte as type Trune) convert1.go:77:12: error: invalid type conversion (cannot use type Tbyte as type Tint64) convert1.go:80:12: error: invalid type conversion convert1.go:82:13: error: invalid type conversion convert1.go:84:11: error: invalid type conversion (cannot use type Trune as type Tbyte) convert1.go:86:12: error: invalid type conversion (cannot use type Trune as type Tint64) convert1.go:88:6: error: invalid type conversion (cannot use type Tint64 as type string) convert1.go:89:12: error: invalid type conversion convert1.go:90:12: error: invalid type conversion convert1.go:92:13: error: invalid type conversion (cannot use type Tint64 as type Tstring) convert1.go:93:11: error: invalid type conversion (cannot use type Tint64 as type Tbyte) convert1.go:94:11: error: invalid type conversion (cannot use type Tint64 as type Trune) fixedbugs/bug195.go:9:21: error: interface contains embedded non-interface fixedbugs/bug195.go:12:21: error: interface contains embedded non-interface fixedbugs/bug195.go:15:15: error: interface contains embedded non-interface fixedbugs/bug195.go:18:2: error: invalid recursive interface fixedbugs/bug195.go:26:2: error: invalid recursive interface fixedbugs/bug195.go:22:2: error: invalid recursive interface fixedbugs/bug251.go:15:2: error: invalid recursive interface fixedbugs/bug251.go:11:2: error: invalid recursive interface fixedbugs/bug374.go:18:34: error: use of undefined type ‘xxxx’ fixedbugs/bug374.go:16:5: error: incompatible type in initialization (incompatible type for method ‘m’ (different number of parameters)) fixedbugs/bug383.go:11:2: error: expected boolean expression fixedbugs/bug383.go:12:2: error: expected boolean expression fixedbugs/bug386.go:10:25: error: incompatible type for return value 1 (type has no methods) fixedbugs/bug386.go:12:25: error: incompatible type for return value 1 (type has no methods) fixedbugs/bug388.go:12:10: error: invalid named/anonymous mix fixedbugs/bug388.go:17:19: error: non-name on left side of ‘:=’ fixedbugs/bug388.go:22:9: error: non-name on left side of ‘:=’ fixedbugs/bug388.go:27:10: error: expected type fixedbugs/bug388.go:32:9: error: expected type fixedbugs/bug388.go:23:14: error: reference to field ‘i’ in object which has no fields or methods fixedbugs/bug388.go:18:18: error: invalid use of type fixedbugs/bug389.go:12:5: error: incompatible type in initialization (different parameter types) fixedbugs/bug390.go:15:24: error: expected integer, floating, or complex type fixedbugs/bug394.go:10:1: error: expected declaration fixedbugs/bug397.go:12:2: error: incompatible type for element 2 key in map construction switch3.go:18:2: error: incompatible types in binary expression switch3.go:22:2: error: incompatible types in binary expression switch3.go:28:2: error: map can only be compared to nil switch3.go:35:2: error: slice can only be compared to nil switch3.go:42:2: error: func can only be compared to nil syntax/else.go:11:9: error: expected ‘if’ or ‘{’ typeswitch2.go:15:2: error: duplicate type in switch typeswitch2.go:19:2: error: duplicate type in switch typeswitch2.go:26:2: error: duplicate type in switch typeswitch2.go:40:9: error: ‘t’ declared and not used R=golang-dev, r CC=golang-dev https://golang.org/cl/5573073
-
Andrew Gerrand authored
R=nigeltao CC=golang-dev https://golang.org/cl/5576054
-
Andrew Gerrand authored
R=golang-dev, dsymonds CC=golang-dev https://golang.org/cl/5577060
-
David Symonds authored
R=rsc CC=golang-dev https://golang.org/cl/5569075
-
Gustavo Niemeyer authored
This solves the ambiguity for "lp.net/project/foo". In these URLs, "foo" could be a series name registered in Launchpad with its own branch, and it could also be the name of a directory within the main project branch one level up. Solve it by testing if the series branch exists in Launchpad and if it doesn't moving the root one level up. R=rsc CC=golang-dev https://golang.org/cl/5577058
-
David Symonds authored
R=rsc, rsc CC=golang-dev https://golang.org/cl/5573075
-
- 26 Jan, 2012 29 commits
-
-
Brad Fitzpatrick authored
Fixes #2186 R=golang-dev, gri, adg CC=golang-dev https://golang.org/cl/5579044
-
James P. Cooper authored
Also allow string values to scan into []byte. Fixes #2788. R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/5577054
-
Rob Pike authored
R=golang-dev, adg, gri CC=golang-dev https://golang.org/cl/5572067
-
Brad Fitzpatrick authored
The new url.URL's parsing can be too canonicalizing for certain applications. By keeping the original request URI around, we give applications a gross escape hatch while keeping the URL package clean and simple for normal uses. (From a discussion with Gary Burd, Gustavo Niemeyer, and Russ Cox.) Fixes #2782 R=golang-dev, rsc, dsymonds CC=golang-dev https://golang.org/cl/5580044
-
Russ Cox authored
Fixes #2609. R=ken2 CC=golang-dev https://golang.org/cl/5572069
-
Russ Cox authored
R=ken2 CC=golang-dev https://golang.org/cl/5569071
-
Andrew Gerrand authored
Fixes #2783. R=bsiegert, rsc CC=golang-dev https://golang.org/cl/5570069
-
Robert Griesemer authored
Also: simpler, more direct test. R=golang-dev, dave.andersen CC=golang-dev https://golang.org/cl/5573070
-
Russ Cox authored
Compare: http://swtch.com/junk/regexp0.html [old] http://swtch.com/junk/regexp.html [new] Especially for packages with large APIs, this makes the overview more promiment, so that it can give the appropriate context for reading the API list. This should help significantly in packages with large APIs, like net, so that the first thing users see is not a jumble of functions but an introduction to the package. R=adg, gri, r, kevlar, dsymonds, rogpeppe CC=golang-dev https://golang.org/cl/5573068
-
Roger Peppe authored
Also fix a shadowed error variable bug. R=golang-dev, rsc CC=golang-dev https://golang.org/cl/5573072
-
Mikio Hara authored
Fixes #2773. R=rsc CC=golang-dev https://golang.org/cl/5571056
-
Luuk van Dijk authored
R=rsc CC=golang-dev https://golang.org/cl/5555072
-
Dmitriy Vyukov authored
It means serious user error that can lead to hard to debug issues under load, log entry will not harm. R=golang-dev, rsc CC=golang-dev https://golang.org/cl/5574075
-
Dmitriy Vyukov authored
Fixes #2781. R=golang-dev, rsc CC=golang-dev, mpimenov https://golang.org/cl/5577053
-
Luuk van Dijk authored
Fixes test/reorder2.go for all cases tripped up with -lll in 5555072 R=rsc CC=golang-dev https://golang.org/cl/5569069
-
Dmitriy Vyukov authored
Fixes #2752. R=golang-dev, mpimenov, r CC=golang-dev https://golang.org/cl/5571062
-
Robert Hencke authored
R=golang-dev, r CC=golang-dev https://golang.org/cl/5572064
-
Rob Pike authored
If there's an error, sometimes you need to stop. Part of issue 2787. R=golang-dev, adg CC=golang-dev https://golang.org/cl/5570068
-
Gustavo Niemeyer authored
R=golang-dev, r CC=golang-dev https://golang.org/cl/5569067
-
Blake Mizerany authored
Fixes #2784 R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/5574073
-
Brad Fitzpatrick authored
The idea is that we add files to the api/ directory which are sets of promises for the future. Each line in a file is a stand-alone feature description. When we do a release, we make sure we haven't broken or changed any lines from the past (only added them). We never change old files, only adding new ones. (go-1.1.txt, etc) R=dsymonds, adg, r, remyoudompheng, rsc CC=golang-dev https://golang.org/cl/5570051
-
James P. Cooper authored
Fixes #2699 R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/5557063
-
Gustavo Niemeyer authored
R=golang-dev, r CC=golang-dev https://golang.org/cl/5577051
-
Brad Fitzpatrick authored
R=golang-dev, adg CC=golang-dev https://golang.org/cl/5573071
-
Brad Fitzpatrick authored
R=golang-dev, iant, adg CC=golang-dev https://golang.org/cl/5574072
-
Gustavo Niemeyer authored
R=golang-dev, bradfitz, r CC=golang-dev https://golang.org/cl/5575056
-
Robert Griesemer authored
R=golang-dev, iant CC=golang-dev https://golang.org/cl/5574071
-
Robert Griesemer authored
Separating Method from Func made the code only more complicated without adding much to the useability/readability of the API. Reverted to where it was, but leaving the new method-specific fields Orig and Level. Former clients (godoc) of doc.Method only used the Func fields; and because Func was embedded, no changes are needed with respect to the removal of Method. Changed type of Func.Recv from ast.Expr to string. This was a long-standing TODO. Also implemented Func.Orig field (another TODO). No further go/doc API changes are expected for Go 1. R=rsc, r, r CC=golang-dev https://golang.org/cl/5577043
-
David G. Andersen authored
R=golang-dev, gri CC=golang-dev https://golang.org/cl/5577050
-
- 25 Jan, 2012 1 commit
-
-
Gustavo Niemeyer authored
This improves the handling of xml.Unmarshal in the xmlapi fix by guessing some of the common types used on it. This also fixes a bug in the partial typechecker. In an expression such as f(&a), it'd mark a as having &T rather than *T. R=golang-dev, rsc CC=golang-dev https://golang.org/cl/5572058
-