I want to ask, how does Zig async backend work currently in 0.13 and what are the plans for its future.
From my experience a per thread work stealing event loop is the best fit for lower level programming, but i am no expert. Also this would make reads/writes from sockets and files utilize kernel level APIs like io_uring, epoll or iocp.
As i said i am no expert, but i haven’t heard of Async for a quite some time and would love to hear where its going.
I think somebody asked this in another thread here:
Also there was a talk with Andrew, https://www.youtube.com/watch?v=5eL_LcxwwHg that he mentions about async, if not mistaken
Thank you, but most of this stuff is from year - half a year ago, around version 0.12, i know 0.14 wont change much about async (which is fine).
I am just asking if there are any plans for it on 0.15+
Ouch
btw. @Narven is a LLM?
(sorry if i interpreted your message wrongly, English is not my first language and that is just a confusing sarcasm)
I apologise, for that… it seems that I’m the joke of the day.
I did not notice that you where talking about 0.15+, but I would assume that what is mention in the video also applies to 0.15+ those things will take long to implement.
PS: English is also not my first language. Sorry you had to be greeted like that on your first post.
Sorry i cant read cyrillic.
I have translated them online and found out you are flaming me for having stupid questions?
I will close this Topic, but i would just like to say that i just tough “oh lets go to the platform Andrew is and ask if there is any planning to start working on async re-implementation to the language since the C++ compiler, is there gona be a change to the way it will work etc.” and i get flamed and accused of being a LLM.
Also would be nice to communicate in english, i am not talking to you in my first-language, the Zig github repo is in english, so lets keep it this way so we can understand each other. (and if you think i am an LLM cuz i cant write proper english, go to hell)
Can i even close this topic?
I think you are getting a little carried away. I don’t see any basis for such convicted accusations.
@dee0xeed Even if you think for some weird reason I’m some AI or LLM or whataver, I think you need to be careful with how you approach people, specially new people.
Just because you think I’m, does not mean that I’m, or even if someone I interact IS what you think I’m.
I would say that least apologise to Bobvan.
Just because I’m interacting with you also make you an LLM?
I dont need any apologies, i dont take stuff on internet personally.
I would just like my question answered by someone who know more then me on a the topic.
Once 0.14 is released and compile speed is at comfortable level, what are the next targets of changes at 0.15 or even 0.16? Is there any plan for starting the work of re-implementing async, and would there be any changes to it? Would there be any support for convenient interacting with kernel APIs for example if i wanted to make statefull TCP server.
If I was a LLM I could probably answer it, but since I’m dumb as f*** to even decide today to come to this forum and be treated liked cr***.
After 48 years… never thought something like this could happen.
Apologise again @Bobvan
The video linked by @Narven is the latest information I know of regarding async.
I don’t know about any official plans but you could of course just implement your own (stackful) coroutines or use one of the few libraries available. Some of them have async io capabilities out of the box I think.