[8pt] Mark all built-in modules with information about yielding

[rosik]

Make fiber stuff well-described again

Product: Tarantool
Since:
Audience/target: Lua devs
Root document: https://www.tarantool.io/en/doc/latest/reference/reference_lua/fiber/
SME: @rosik
Peer reviewer: @ documentarian name

Details

Documentation about implicit cases is very poor. I believe it deserves another chapter in doc.

What information I'd like to see there:

• List ALL functions that yield explicitly. And when do they. For example, channel:get() is tricky and yields only occasionally.
• Mark ALL those functions within their sections - fio, netbox, http, socket, log (!), etc.
• Every implicit yield may raise upon wakeup if the fiber was cancelled.
• fiber.cancel doesn't yield, but still raises "fiber is cancelled" error.
• Please mention requirements for triggers too.

Definition of done

[Totktonada]

I would also create a documentation page, which describes how fibers serve requests.

[Totktonada]

Related: #1648.

[artur-barsegyan]

This is another task that cannot be done with the help of documentaries. Documenters do not have the competence to determine exactly whether a yield is a function or not.

I see a simple solution:

• come up with how we will write in the reference that the function can be displayed
• create a google sheet with tabs for each module in Tarantool
• give a link to the required tabs for each subcommand in Core

Then transfer this information to rST.

[artur-barsegyan]

And we should rename this issue into "Mark all built-in modules with information about yielding"