nb icon indicating copy to clipboard operation
nb copied to clipboard

Minimal and reusable non-blocking I/O layer

Results 9 nb issues
Sort by recently updated
recently updated
newest added

While the documentation lists that blocking (busy wait, `block!`) and in asynchronous operation, there are no examples for the latter, and the link into the futures documentation is semantically broken...

I am using this macro derivative for an private project for a while now and decided to see whether others (like you) can make use of it as well. Basically...

With futures becoming standardized and integrated into the core library, I feel like this crate has less reason to exist. The biggest part of this crate is `type nb::Result =...

discussion

In reference to @japaric's comment [here](https://github.com/japaric/nb/pull/12#issuecomment-372077362). > In my mind operations that return nb::Result signal that they can't be _started_ and completed right now via WouldBlock but once you get...

discussion

I believe there is a problem with the design of `nb` as it only allows for "one level" of asynchronicity, which is glossed over via the stubbed out definitions for...

discussion

There seem to be a few problems that are caused by side-effects of calls that return WouldBlock: * https://github.com/rust-embedded/embedded-hal/issues/123 is about how to start a new ADC reading when an...

discussion

I think the title says it all :) What do you think about this?

This is a particularly nasty issue that I spent several days tracking down. See knurling-rs/defmt#723 for another example.