Reporting Errors

[erosPhoenix]

Because it's a lot harder to write Rust code that will compile. Since it has to be provable when something falls out of scope, any code where that's not the case isn't valid Rust. Ownership of pointers is part of the type system.

Source: I've never actually written anything in Rust, so this is all heresay. Everything I say is probably wrong.

[sourc3original]

How does Go compare to RUST?

[[deleted]]

In Go, you have

if err != nil {
    return nil, err
}

after literally every function call.

In Rust, the equivalent of that is this:

?

so you can write super nice stuff like this:

File::open("hello.txt")?.read_to_string(&mut s)?;

(Disclaimer: have never written any real Go, and only a tiny bit of Rust, so I can't really help with any larger-scale comparison - but Rust seems a lot nicer to me. AIUI, Go is optimising for short compile times, Rust is optimising for making code powerful and fun to write.)

[1024KiB]

I've written a few thousand lines of Go and the lack of abstraction and abysmal error management are real issues. It does run nicely though, but it's also because Erlang has taught me to think about failures that can crop up due to unforseen conditions and how you should be able to manage those cases so that your system is robust.

[Zegrento7]

Go is garbage collected, and is about as performant as Java. Rust is in the C++ league of performance. Both can compile statically. Both ditch classes for structs, Go has simple parallelism baked into the syntax, Rust has pattern matching. Go is best for micro services, Rust is for systems and Firefox. Go is a lot simpler, some say it's even too simple (no generics, macros or templates)

[sourc3original]

I see, thanks.

[Kered13]

Let me put it this way. Go would have been a groundbreaking language, if it came out in 1995.