Christopher Hunt

So you're stating that a design choice should be based in an implementation detail?

> It really depends how rust implements ITS threading model. I'm basing this request entirely in the doc generally available and therefore Rust's current approach. It appears that threads are...

FYI I've implemented https://github.com/nrf-rs/nrf-hal/pull/337 on the assumption that the read offset is a multiple of READ_SIZE. It'd be great to get confirmation on this. Thanks.

> Yeah, the current docs are missing specifying that `offset` and `bytes.len()` are multiples of `READ_SIZE`. > > However it's true that the majority of chips (all?) have READ_SIZE=1. Maybe...

Thanks for the explanations. Do you want a PR for the elimination of the READ_SIZE requirement?

Are you able to elaborate on your use case? It appears as though you want to determine whether an AMQP broker is reachable from looking at your example. If that's...

> But when your application is starting, you may want consider it fully started (healthy) only when the connexion to the broker is up, and not before. Without this materialized...

> I'm not sure to understand how I can get this kind of behavior without having to modify the implementation of the AmqpSourceStage. What do you have in mind? ```scala...

Do you really want your program to stop if it loses connectivity with AMQP? Losing connectivity is quite normal. Have you considered `RestartSource` and friends? (https://doc.akka.io/docs/akka/2.5.5/scala/stream/stream-error.html) Also, how about using...

Any further thinking on this? I could try a PR with some guidance. Thanks.