Just when I thought I fixed the error and finally made rustc happy, I got loads of other errors.

They always come in two waves. First the simple things like syntax errors or incorrect types, then it can analyse the code enough to find all the ownership-related problems.

But it is progress, yo!

@deadlyRants I think I'm past ownership errors. I got generic type/trait errors now.

If you want the compiler to find even more errors, try OCaml...

And you should be lucky to get them presented on a silver platter like that!

@rantsauce Oh, good luck ;)

Traits (or rather trait objects) are pretty much the one thing I almost never bother with. Maybe it's just me but I find error messages in that area really unhelpful, and the included suggestions never work.

@deadlyRants It's get confusing even (specially?) for the compiler.

Have you tried to use VSCode + Rust-Analyzer? I started with CLion but it stopped working for me after a few weeks. Rust Analyzer is just awesome. Seeing types is super helpful and errors on the go prevent the waves of errors after a feature is done.