A proposal to include the spawn keyword in send_future and friends

[huntc]

I'd like to propose that we rename the scope's send_future method to spawn_send_message, as this may more accurately describe what it is doing and could provide a higher degree of assurance.

When looking at the example of using fetch with async/await, it wasn't clear to me that a spawn was taking place. I feel that it is important to understand that the spawn is occurring so we also understand that our component doesn't become unresponsive to other messages and events. As send_future is a spawned flavour of send_message, spawn_send_message may therefore lead to a better understanding of what is happening.

Similarly:

• send_future_batch could become spawn_send_message_batch
• callback_future could become spawn_callback
• callback_future_once could become spawn_callback_once

Preliminary discussions: https://discord.com/channels/701068342760570933/703449306497024049/886381533815009331

[intendednull]

Personally, in the context of an actor system, blocking wouldn't make much sense. Not sure we need to be more specific/verbose here, since there isn't a non-spawning alternative. Improving docs might be all we need to clear up any more confusion.

[huntc]

Improving the docs may help, but changing the name could help avoid needing to visit the docs. I should add that I've arrived at this thinking from the point of being a user of Yew and not a developer, in case that helps.