Edmond, async stuff is like having another thread. So "spawn" fits but also "throw" in terms of what it does. At least what it actually does (at least what it must) at a low level.
> The `spawn` keyword maybe the right keyword to use but it seems more weird, can we find another keyword to use other than that? Spawning a child thread means you don't care about if it will ever finish. The main loop may finish before it receives something from the child process unless it's instructed to wait for it and the child process will just die. For me the "spawn" fits On Sun, Mar 16, 2025 at 8:35 PM Edmond Dantes <edmond...@gmail.com> wrote: > Hello, Vincent. > > > > > Personally, i love the formal RFC for it's low level accessibility and > this new RFC isn't that bad. > > > If you mean classes like SocketHandle and so on, then the low-level API > can be available as a separate extension. > > > > > The `spawn` keyword maybe the right keyword to use but it seems more > weird, can we find another keyword to use other than that? > > Most languages i've seen make use of only the `async/await` keyword. > > > > Yes, spawn has the downside of being more associated with threads. Here > are some other possible options: > > - launch — like in Kotlin > - go — the shortest option > > async is not the best choice because it looks more like an attribute, > while we would prefer to use a verb. > > From a brevity standpoint, I like go, but after that, Go developers will > have to implement the $ symbol for all variables :) > > --- > > Ed. > >> -- Iliya Miroslavov Iliev i.mirosla...@gmail.com
