This website requires JavaScript.
About
Status
₊˚⊹Discord
Explore
Register
Sign in
Reference in a new issue
Blame
Copy permalink
Reference in a new issue
Copy permalink
DKB
/
zml
Star
0
Fork
You've already forked zml
0
mirror of
https://github.com/zml/zml.git
synced
2026-11-16 19:11:09 +00:00
Code
Issues
23
Releases
1
Packages
Activity
steeve/tt
zml
/
async
/
executor.zig
182 lines
4.7 KiB
Raw
Permalink
Normal View
History
async: vendor zigcoro and unify APIs (#152) This PR merges zigcoro inside the repo and reworks its internals to play well with `stdx.meta`. It also adds `Channel.try_{send,recv}` methods as well as dynamically sized channels (with a `comptime` capacity). Although not used, it also introduces a `PoolStackAllocator` for allocating coroutine stacks from a pool
2025-01-14 19:33:16 +01:00
async should only use sync logging (#225) currently using async.LogFn inside async runtime itself panics. So I'm avoiding that by forcing async.zig logging to go through std.log.defaultLog which is synchronous. you can reproduce the crash by changing log level to .debug
2025-04-16 09:35:18 +02:00
async: vendor zigcoro and unify APIs (#152) This PR merges zigcoro inside the repo and reworks its internals to play well with `stdx.meta`. It also adds `Channel.try_{send,recv}` methods as well as dynamically sized channels (with a `comptime` capacity). Although not used, it also introduces a `PoolStackAllocator` for allocating coroutine stacks from a pool
2025-01-14 19:33:16 +01:00
async should only use sync logging (#225) currently using async.LogFn inside async runtime itself panics. So I'm avoiding that by forcing async.zig logging to go through std.log.defaultLog which is synchronous. you can reproduce the crash by changing log level to .debug
2025-04-16 09:35:18 +02:00
async: vendor zigcoro and unify APIs (#152) This PR merges zigcoro inside the repo and reworks its internals to play well with `stdx.meta`. It also adds `Channel.try_{send,recv}` methods as well as dynamically sized channels (with a `comptime` capacity). Although not used, it also introduces a `PoolStackAllocator` for allocating coroutine stacks from a pool
2025-01-14 19:33:16 +01:00
async should only use sync logging (#225) currently using async.LogFn inside async runtime itself panics. So I'm avoiding that by forcing async.zig logging to go through std.log.defaultLog which is synchronous. you can reproduce the crash by changing log level to .debug
2025-04-16 09:35:18 +02:00
async: vendor zigcoro and unify APIs (#152) This PR merges zigcoro inside the repo and reworks its internals to play well with `stdx.meta`. It also adds `Channel.try_{send,recv}` methods as well as dynamically sized channels (with a `comptime` capacity). Although not used, it also introduces a `PoolStackAllocator` for allocating coroutine stacks from a pool
2025-01-14 19:33:16 +01:00
async: async mutex on log and fixes on ResetCondition (#166) Stop using a real mutex for the `logFn` and use an `Mutex` and allow for a fallback logger if outside a coroutine.
2025-01-24 20:58:14 +01:00
async: vendor zigcoro and unify APIs (#152) This PR merges zigcoro inside the repo and reworks its internals to play well with `stdx.meta`. It also adds `Channel.try_{send,recv}` methods as well as dynamically sized channels (with a `comptime` capacity). Although not used, it also introduces a `PoolStackAllocator` for allocating coroutine stacks from a pool
2025-01-14 19:33:16 +01:00
async: async mutex on log and fixes on ResetCondition (#166) Stop using a real mutex for the `logFn` and use an `Mutex` and allow for a fallback logger if outside a coroutine.
2025-01-24 20:58:14 +01:00
async: vendor zigcoro and unify APIs (#152) This PR merges zigcoro inside the repo and reworks its internals to play well with `stdx.meta`. It also adds `Channel.try_{send,recv}` methods as well as dynamically sized channels (with a `comptime` capacity). Although not used, it also introduces a `PoolStackAllocator` for allocating coroutine stacks from a pool
2025-01-14 19:33:16 +01:00