wren/test/core/fiber/transfer_to_done.wren

var a = Fiber.new {
  IO.print("run")
}

a.call() // expect: run
a.transfer() // expect runtime error: Cannot transfer to a finished fiber.
Revise low level fiber semantics to play nicer with schedulers. Now that I'm starting to write a real async scheduler on top of Wren's basic fiber API, I have a better feel for what it needs. It turns out run() is not it. - Remove run() methods. - Add transfer() which leaves the caller of the invoked fiber alone. - Add suspend() to return control to the host application. - Add Timer.schedule() to start a new independently scheduled fiber. - Change Timer.sleep() so that it only transfers control to explicitly scheduled fibers, not any one. 2015-08-30 22:15:37 -07:00			`var a = Fiber.new {`
			`IO.print("run")`
			`}`

			`a.call() // expect: run`
			`a.transfer() // expect runtime error: Cannot transfer to a finished fiber.`