honor `ErrorKind::Interrupted` in `write_all()`? about embedded-hal HOT 4 OPEN

Interesting question.
I would ask then how often should it retry. Either we create an endless loop or we define an arbitrary number which will be difficult to agree upon.
Given the general character or e-io-async, I think the caller is better positioned to put a loop on the call in this case.

from embedded-hal.

ErrorKind::Interrupted is annoying unix legacy-ish. I don't think anyone uses it intentionally anymore, especially now that async exists? it doesn't really exist on embedded, and i'd say it shouldn't exist.

So perhaps another option is to make embedded_io_adapters::FromStd do the retry on the write() method, so we keep Interrupted errors to the boundary of embedded-io instead of letting them in?

from embedded-hal.

That sounds like a really good idea. Should we then also remove ErrorKind::Interrupted?

from embedded-hal.

probably, yes...

from embedded-hal.