chmod777Mar 15
Wish the people maintaining embedded-io would just support all of the errors from std::io. If you want to be the common denominator be it. If you only want to support io in the context of a stream readers state it. Don't pretend you are something you aren't.
#rust #embedded #motivational
Show threadMichał FitaMar 16
@chmod777 Not sure if it makes sense, `std::io::` would have all errors general kernel ring OS would have, some of these issues would never happen on traditional RTOS.
Show threadchmod777Mar 17
@michalfita
I could think of reasons to support all of https://doc.rust-lang.org/std/io/enum.ErrorKind.html
ErrorKind in std::io - Rust

A list specifying general categories of I/O error.

Show threadMichał Fita
@chmod777 For example, networking on embedded systems is usually not I/O based, hence network related errors are pointless; then probability you'd use NFS on any is again very low and plenty of these errors are related to that.
Mar 17 at 11:23amWeb
Show threadchmod777Mar 17
@michalfita ehh? No
Show threadchmod777Mar 17
@michalfita I think you are assuming somebody would never use a filesystem in an embedded environment and you would be wrong. Most of these errors are file system based if you looked at them. not netwrok
Show threadMichał FitaMar 17
@chmod777 NFS is Network File System, very specific to UNIX operating systems and with implications none small form factor RTOSes would be able to handle. There are at least three error kinds there specific to this.
Show threadchmod777Mar 17
@michalfita Let the user decide how to handle the error. This is a non exhaustive list anyways. If somebody doesn't want to handle the error let them. Using Other for everything is the equally bad option. You wont know in what context emedded_io::ErrorKind gets used in and thats Ok. just support them all
Show threadchmod777Mar 17
@michalfita Not every implementation is as dim witted as the most common denominator.