Matt Topol
It also looks like the Rust devs are running into this problem too: https://internals.rust-lang.org/t/who-is-doing-read-proc-self-maps-1024-at-startup/17348
@cherrymui I only included the rust post because it was referring to the same scenario of calling `pthread_getattr_np` in hindsight it was probably not really great to include as the...
Looks like you're right! I updated the code from the reproducer to the following: ```c #include "libtrivial.h" #include #include #include void* f(void*) { int a = 0; for (int i...
@cherrymui @mknyszek any updates here?
Thanks for the update! That's about what I was expecting the fix would end up being
@westonpace your last example confuses me a bit, particularly because the entire purpose of this is to create a *push-based* approach for async handling, rather than a pull-based approach. Below...
@westonpace I completely forgot to address the other suggestion where you *did* put the waker directly into the interface lol ```c struct Waker { // Signal to the producer that...
I just want to consolidate the discussion here, please let me know if I missed anything or got anything wrong. ## Changes to the proposal * Either remove the `extension`...
> There's the partial compromise option: Something like `int on_next_task(ArrowAsyncDeviceStreamHandler*, ArrowArrayTask*)` ?
> I'm not quite sold on this if we want to have a callback based API. Though I understand wanting to have the most efficient possible theoretical API. At least...