what is the difference between ev/call and ev/go ?

[lost22git]

except ev/go has supervisor and supports fiber args

[sogaiu]

Here is some text from the website:

The ev/call function takes a function as well as its arguments and calls that function inside a new task. ev/call returns the newly created task fiber immediately.

The more general way to start new tasks is ev/go, which takes as an argument a fiber to be resumed by the event loop scheduler. ev/go allows the programmer to customize fiber flags as well as specify a supervisor channel for the newly created task.

via: https://janet-lang.org/docs/event_loop.html#Creating-Tasks

Also, below is the current implementation of ev/call:

janet/src/boot/boot.janet

Lines 3817 to 3823 in b27c830

	(defn ev/call
	```
	Call a function asynchronously.
	Returns a fiber that is scheduled to run the function.
	```
	[f & args]
	(ev/go (fn :call [&] (f ;args))))

Does any of that help?

[lost22git]

Does it mean that ev/go can totally replace ev/call ? Or what's the scene use ev/call rather than ev/go?

[sogaiu]

Regarding background on ev/call and ev/go...

According to this commit on 2020-07-07:

Add ev/call.

This is a common operation, and making fibers manually can be tedious.

Later, there was this commit on 2021-08-31:

Allow passing a function to directly to ev/go.

Makes ev/call less useful but ev/go more useful. No need
to construct as many identical intermediate fibers.

IIUC, originally, ev/go's first argument had to be a fiber, but this was changed later (the second commit above).

[lost22git]

Thanks,