wren/test/language/break/in_while_loop.wren

var i = 0
while (true) {
  i = i + 1
  System.print(i)
  if (i > 2) break
  System.print(i)
}
// expect: 1
// expect: 1
// expect: 2
// expect: 2
// expect: 3
Break statements. 2013-12-24 10:15:50 -08:00			`var i = 0`
			`while (true) {`
			`i = i + 1`
"IO" -> "System". Get rid of the separate opt-in IO class and replace it with a core System class. - Remove wren_io.c, wren_io.h, and io.wren. - Remove the flags that disable it. - Remove the overloads for print() with different arity. (It was an experiment, but I don't think it's that useful.) - Remove IO.read(). That will reappear using libuv in the CLI at some point. - Remove IO.time. Doesn't seem to have been used. - Update all of the tests, docs, etc. I'm sorry for all the breakage this causes, but I think "System" is a better name for this class (it makes it natural to add things like "System.gc()") and frees up "IO" for referring to the CLI's IO module. 2015-09-15 07:46:09 -07:00			`System.print(i)`
Allow statement bodies for flow control. This means this works now: if (foo) return bar 2013-12-24 10:27:48 -08:00			`if (i > 2) break`
"IO" -> "System". Get rid of the separate opt-in IO class and replace it with a core System class. - Remove wren_io.c, wren_io.h, and io.wren. - Remove the flags that disable it. - Remove the overloads for print() with different arity. (It was an experiment, but I don't think it's that useful.) - Remove IO.read(). That will reappear using libuv in the CLI at some point. - Remove IO.time. Doesn't seem to have been used. - Update all of the tests, docs, etc. I'm sorry for all the breakage this causes, but I think "System" is a better name for this class (it makes it natural to add things like "System.gc()") and frees up "IO" for referring to the CLI's IO module. 2015-09-15 07:46:09 -07:00			`System.print(i)`
Break statements. 2013-12-24 10:15:50 -08:00			`}`
			`// expect: 1`
			`// expect: 1`
			`// expect: 2`
			`// expect: 2`
			`// expect: 3`