rustic_result VS gopl.io

Self promotion moment:

If you enjoy the Result/Either type and API in Rust, I made this project just for this: https://github.com/linkdd/rustic_result

I also made https://github.com/linkdd/rustic_maybe/tree/main for an Option/Maybe type.

NB: Those are not types, but I'm waiting for set theoretic types to update those libs :)

It's missing the Erlang/Elixir pattern of returning a tuple `{:ok, T}` or `{:error, E}`, where we can then use pattern matching, or `with` expressions, etc...

To be fair, it is very similar to a `Result` type, which is why I made this library a while ago: https://github.com/linkdd/rustic_result

I intend to add a pipeline operator similar to Elixir, to be used with an std::result module which will provide functions to ease writing such complex code. I may take inspiration on an Elixir library I wrote a while ago: https://github.com/linkdd/rustic_result

A while ago, I made this library https://github.com/linkdd/rustic_result

I also made a library for working with `{:ok, value}` and `{:error, reason}` in Elixir: https://github.com/linkdd/rustic_result

Thanks to the pipeline operator and pattern matching, it makes pretty easy to read pipelines. It does not completely replace the with statement (that was not the point) but it simplified a lot of code.

Go never changed as much as Java does in each major release, so old books are still relevant. https://www.gopl.io/ is fine if you read about generics and some new standard library modules somewhere else later.

The Go Programming Language book.

The GOPL book is good one to start with, if you prefer reading books. https://www.gopl.io/

Not that they are leet code style, but some exercises from "The Go Programming Language" are really worth having a look at, also most solutions are available at https://github.com/adonovan/gopl.io

What part(s) are you struggling with and how are you learning? The Go Programming Language is slightly outdated but is an excellent intro. You can read the first chapter free. Also the resources on https://go.dev/learn/ are great. If I were you, I would come up with an idea you're excited about and build it.

For a deeper dive, I’d recommend The Go Programming Language - a fantastic resource covering a broader landscape of the language than just concurrency.

"Low-level programming" is chapter 13, both in the version I have and on https://www.gopl.io/ -- the rest is all somewhat crucial stuff, except for maybe reflection.

Is this the "The Go Programming Language" you mentioned?