Rust already has most of what I want from error handling: explicit control flow, errors as values, and concise propagation with ?. The friction comes when deciding what to put in the error half of Result. We often end up choosing between precise types that require boilerplate and convenient types that hide which errors can occur. But precision and convenience do not have to be competing goals. Error types should compose as easily as the functions that return them.
  • SorteKanin@feddit.dkOP
    12·
    2 days ago

    So basically their argument is that the missing piece is anonymous sum types. I tend to agree! It would be amazing to have that as a language feature, i.e. Result<(), FooError | BarError>. Unfortunately that is unlikely to arrive to the language for a loooong time… But I think I will definitely try out this library in the meantime.

    • BB_C@programming.dev
      2·
      2 days ago

      A language feature is not needed because macros exist.

      I would even argue that perhaps the most important role macros play is blocking adding endless language features 😉

      • SorteKanin@feddit.dkOP
        2·
        2 days ago

        Macros are often not very ergonomical to use compared to language features.

        Also, why anonymous product types but not anonymous sum types? It seems kind of weird to me. Anonymous sum types can be just as useful as anonymous product types, as the blog post illustrates quite well I think.

        • BB_C@programming.dev
          2·
          2 days ago

          The language wouldn’t have lost much without tuples actually. But they do at least have direct pattern destructuring utility. Anonymous enums don’t.

          They also don’t pose potential future awkwardness if/when variant types become a thing.

        • TehPers@beehaw.orgEnglish
          2·
          2 days ago

          While I agree with you that anonymous sum types are useful, the language designers tend to avoid anything that might include a hidden cost (in this case either the size of the enum or cost of boxing). Something along those lines might end up in the language eventually, though.

  • Ephera@lemmy.ml
    4·
    2 days ago

    Damn, this looks like it might solve my pain points with error handling. Will have to see, if it replaces them with new pain points, since error handling is fundamentally hard, but at least, it isn’t starting completely from scratch…

  • TehPers@beehaw.orgEnglish
    3·
    2 days ago

    I like the general idea (not a fan of the syntax but whatever). The one thing I’m not seeing is non-exhaustive error types. For example, in a library, you likely want to say “these errors are known to be possible, and some errors may be added in the future”. Without non-exhaustive error types, this would mostly be useful exclusively in applications, not libraries. Of course, syntax-wise, you can just do (E1, E2, ...) or something to mark it non-exhaustive (if you were to add this to the language directly).

    Either way, I agree that defining errors is needlessly extraordinarily verbose. I’m tempted to make a simple one-line macro to union a bunch of error types into an enum. (or use this library since I misread this as a language proposal lol) This, of course, falls apart when a function might use the same error type for multiple errors, or if it uses custom errors with no inner errors, but those cases are what thiserror is for.

    • lad@programming.devEnglish
      1·
      2 days ago

      I’m not sure non-exhsustive makes sense — you want the caller to handle everything you may return to them, and the new errors won’t be handled. Maybe a default branch in the handler could do, though

      • Ephera@lemmy.ml
        4·
        2 days ago

        Had to just think about why #[non_exhaustive] exists, so perhaps this helps you as well:

        Imagine you’re developing a really important core library, something like TCP. And then other libraries depend on your library.
        Now, if you change your implementation, you may need to introduce a new error case, even though the rest of the API still works the same.

        You have two choices to deal with that:

        • Release version 2.0, because that’s a breaking change. Each library that depends on you needs to manually upgrade to version 2.0. Some never will, because they’re unmaintained. Any application that ships your library as a transitive dependency will need to ship both, version 1.0 and version 2.0, for the next few years until the last of their direct dependencies has upgraded to 2.0 or been removed.
        • Or: You’ve declared that error enum #[non_exhaustive] before going 1.0 and therefore forced all depending libraries to implement a default match case. You can sneak in the new error case in version 1.1 without all those depending libraries needing to manually upgrade. The ecosystem does not split in half between 1.0 vs. 2.0.

        Obviously, if it’s a really egregious new error case that needs specific handling, then you might still want to release version 2.0, but by adding the #[non_exhaustive], you can decide later on and if you are such a central library, there’s definitely going to be situations where you want to make use of it.

      • TehPers@beehaw.orgEnglish
        3·
        2 days ago

        Maybe a default branch in the handler could do, though

        This is exactly what it’s for. #[non_exhaustive] forces you to add a default branch when matching on the error. It’s already used a lot, so without a way to do that, it becomes less useful in library code.