Oh neat, just realized `log` + `bumpalo` probably work really well together! Each time a message is created it can be stored in the bump allocator. Then every n messages, or when `Log::flush` is called we take a lock on stdout, write all messages, and reset the allocator!
Ohh, yes of course! Should be fairly straight forward to build with crossbeam's queues! Out of curiosity: what do you mean by "idle loop" here?
-
-
Embedded programs usually have an "idle loop" which runs when nothing else needs doing (ie. there are no pending interrupts that need to be served). This is the lowest-priority code that runs in an application. Often this loop is just "loop { wait for interrupt }".
-
Ohhh, I like this a lot! Browser have a similar concept -- `RequestIdleCallback`. This allows scheduling work during idle time OR if a duration has elapsed. I've been wondering for a while now if we could bring this to async runtimes as well; think it could make sense! Ty! :D
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.