Result<T, E> in TypeScript: A Better Alternative to Throwing

7 months ago by monica_b1998 to c/learn_programming

Learn how to use Result in TypeScript for safer, clearer error handling without relying on exceptions everywhere.

artwork 2 points 7 months ago

This is quite interesting, since the article states absolutely nothing about Go language.
Since, it's the most common or even fairly standard technique in the language:

func Hello(name string) (string, error) {
    // If no name was given, return an error with a message.
    if name == "" {
        return "", errors.New("empty name")
    }
    // ...
}

Source: go.dev/doc/tutorial/handle-errors

save

path: 0 22939500, hotness: undefined, score: 2, children: 3

lbfgs 5 points 7 months ago

Go's val, err := maybeDoThing() pattern isn't the same thing because it's not a discriminated union like Rust's Result or C++'s std::expected or the Typescript example in the article. Moreover, due to restrictions in Go's generics, it's impossible to implement what is imo the most attractive pattern enabled by the discriminated union Result types - monadic operations.

save

path: 0 22939500 22944631, hotness: undefined, score: 5, children: 0

felsiq 3 points 7 months ago

Ditto for rust, although I didn’t read the article to know if they mentioned that one lol

save

path: 0 22939500 22940491, hotness: undefined, score: 3, children: 1

artwork 2 points 7 months ago

Thank you! Apparently, they did not mention Rust, too ^^"

save

path: 0 22939500 22940491 22940659, hotness: undefined, score: 2, children: 0

Posting Etiquette

Ask the main part of your question in the title. This should be concise but informative.

Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

Posting Etiquette

Ask the main part of your question in the title. This should be concise but informative.

Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient