wren/test/core/fiber/call_transferred.wren

var main = Fiber.current

var fiber = Fiber.new {
  System.print("transferred")
  System.print(main.transfer())
  System.print("called")
}

fiber.transfer() // expect: transferred
System.print("main") // expect: main
fiber.call()     // expect: null
                 // expect: called
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 main = Fiber.current`

			`var fiber = Fiber.new {`
"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("transferred")`
			`System.print(main.transfer())`
			`System.print("called")`
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			`}`

			`fiber.transfer() // expect: transferred`
"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("main") // expect: main`
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			`fiber.call() // expect: null`
			`// expect: called`