On Error Handling in Rust

Post by twic » Sat, Oct 18, 2014, 1:01 PM UTC

m0th87 wrote: post #33

carterschonwald wrote: post #12

Earlier quoted context omitted.

nope, its all compile time. its just that instead of deciding which impl to pick based upon information X, youre using a pair of pieces of information (X,Y) Edit, also I think the "convertable" class idea is nearly expressible using associated types in rust today,but im not 100% certain about that

Wikipedia implies that multiple dispatch is done by run-time time analysis in OO languages, which does not apply to Haskell or Rust: https://en.wikipedia.org/wiki/Multiple_dispatch Maybe it's being pedantic, but I can't tell. Are Haskell's type classes strictly as flexible as multiple dispatch?

The proposed Rust feature sounds like overloading rather than multiple dispatch as it is usually understood.

Post by kybernetikos » Sat, Oct 18, 2014, 9:15 PM UTC

sergiosgc wrote: post #39

krig wrote: post #36

Earlier quoted context omitted.

I see, yes. Implementation-wise, I don't think this is a problem, the inner function can easily be inlined by the compiler. But language-wise I agree that it is somewhat ugly. Some kind of sugar over this kind of construction would be nice.

I was not thinking in terms of compilation result. My problem with this solution is readability. Functions get extracted in the name of reusability. When they are called just once, they do not serve that purpose, and just use space in the programmers mental map of the program. However, I imagine your type of solution could be used in a macro, like jeremyjh suggested in a parallel comment, producing simple code and th…

> My problem with this solution is readability. Functions get extracted in the name of reusability

In my opinion one of the biggest benefits of functions is the ability to name pieces of code. I've worked with a number of teams where a single line function with a single caller and a descriptive name is preferred to a line that needs a comment to say what it does.

Re: On Error Handling in Rust

Re: On Error Handling in Rust