#rustlang friends, what crate lib error naming convention do you prefer?
-
-
foo::Error is the one I try to stick to and personally like the best. What makes it confusing is are many offenders in the std library bool and utf8 errors in str https://doc.rust-lang.org/std/str/struct.ParseBoolError.html … https://doc.rust-lang.org/std/str/struct.Utf8Error.html … send and recv errors in mpsc https://doc.rust-lang.org/std/sync/mpsc/struct.SendError.html …
-
..right next to modules that do follow the guidelines: fmt and io for example https://doc.rust-lang.org/std/fmt/struct.Error.html … https://doc.rust-lang.org/std/io/struct.Error.html … I can understand why ( multiple tightly focused errors under a module ) but it does send a mixed message :/
- 5 more replies
New conversation -
-
-
then it's better to change guidelines, because when you have at least 2 external modules with same "Error", you have no other choice but create aliases.
-
What's wrong with using qualified names like `foo::Error` and `bar::Error` in the code?
- 1 more reply
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.