aboutsummaryrefslogtreecommitdiff
path: root/test/closure.go
AgeCommit message (Collapse)Author
2012-07-01test: enforce 1 proc in the testDmitriy Vyukov
otherwise it fails spuriously with "newfunc allocated unexpectedly" message when run with GOMAXPROCS>1 (other goroutine allocates). R=golang-dev, dsymonds CC=golang-dev https://golang.org/cl/6347056
2012-02-19test: [a-c]: add introductory comments to testsRob Pike
Very few of the compiler regression tests include a comment saying waht they do. Many are obvious, some are anything but. I've started with a-c in the top directory. More will follow once we agree on the approach, correctness, and thoroughness here. zerodivide.go sneaked in too. R=rsc, r CC=golang-dev https://golang.org/cl/5656100
2012-02-16test: use testlib (first 100)Russ Cox
X ,s;^// \$G (\$D/)?\$F\.go *$;// compile;g X ,s;^// \$G (\$D/)?\$F\.go && \$L \$F\.\$A *$;// build;g X ,s;^// \$G (\$D/)?\$F\.go && \$L \$F\.\$A && \./\$A\.out *$;// run;g X ,s;^// errchk \$G( -e)? (\$D/)?\$F\.go *$;// errorcheck;g R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/5656082
2012-02-06runtime: delete UpdateMemStats, replace with ReadMemStats(&stats).Rémy Oudompheng
Unexports runtime.MemStats and rename MemStatsType to MemStats. The new accessor requires passing a pointer to a user-allocated MemStats structure. Fixes #2572. R=bradfitz, rsc, bradfitz, gustavo CC=golang-dev, remy https://golang.org/cl/5616072
2012-01-10gc: test that asserts closures are not wrapped when they don't have closure ↵Luuk van Dijk
vars. R=rsc, bradfitz CC=golang-dev https://golang.org/cl/5529060
2011-11-13gc: remove func, map compareRuss Cox
R=ken, ken CC=golang-dev https://golang.org/cl/5373079
2010-12-13gc: issue 1231Russ Cox
Fixes #1231. R=ken2 CC=golang-dev https://golang.org/cl/3627041
2010-03-24delete all uses of panicln by rewriting them using panic or,Rob Pike
in the tests, println+panic. gofmt some tests too. R=rsc CC=golang-dev https://golang.org/cl/741041
2009-07-28make every func literal expression allocate,Russ Cox
so that == on func means that the functions originated in the same execution of a func literal or definition. before, there was an inconsistency: func() {x++} != func() {x++} but func() {} == func() {} this CL makes the second case != too, just like make(map[int]int) != make(map[int]int) R=r DELTA=202 (71 added, 62 deleted, 69 changed) OCL=32393 CL=32398
2009-03-03Automated g4 rollback of changelist 25024,Russ Cox
plus significant hand editing. Back to T{x} for composite literals. R=r OCL=25612 CL=25632
2009-02-13convert composite literals from { } to ( ).Russ Cox
only non-trivial changes are in convlit1.go golden.out R=gri OCL=25019 CL=25024
2009-02-06closures - runtime and debugger support, test caseRuss Cox
R=r DELTA=257 (250 added, 1 deleted, 6 changed) OCL=24509 CL=24565
7apu2bq3rhoylwmucxizk54afw5jyda7pho4j5zdcqpwkufke7zdzwad.onion